[Fix][jjaeroong]: 팟 관련 데이터 삭제 순서 수정

[jjaeroong]

PR 타입(하나 이상의 PR 타입을 선택해주세요)

• 기능 추가
• 기능 삭제
• 버그 수정
• 의존성, 환경 변수, 빌드 관련 코드 업데이트
• 리팩터링

반영 브랜치

ex) feat/login -> dev

작업 내용

ex) 로그인 시, 구글 소셜 로그인 기능을 추가했습니다.

테스트 결과

ex) 베이스 브랜치에 포함되기 위한 코드는 모두 정상적으로 동작해야 합니다. 결과물에 대한 스크린샷, GIF, 혹은 라이브

Summary by CodeRabbit

• 신규 기능

  • 해당 없음

• 버그 수정

  • 크리에이터가 모집 중인 팟을 삭제할 때 간헐적으로 발생하던 삭제 실패/충돌 가능성을 해소했습니다.
  • 저장된 항목 및 연관 데이터 정리를 선행한 뒤 팟을 삭제하도록 절차를 일관화하여 데이터 정합성을 개선했습니다.

• 리팩터링

  • 중복된 삭제 호출을 제거해 처리 흐름을 단순화하고 유지보수성을 높였습니다.

• 문서

  • 해당 없음

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

handleCreatorPotDeletion 내부에서 초기의 중복 삭제 호출을 제거하고, 모집 중인 potId들에 대한 삭제 순서를 유지한 채 후반부의 potRepository.deleteByUserIdAndPotIds 호출만 남겼습니다. 모집 정보, 지원서, 스크랩 삭제 로직은 그대로이며, 퍼블릭 API 시그니처와 예외 처리 변화는 없습니다.

Changes

Cohort / File(s)	Change summary
사용자 생성자 포트 삭제 정리 src/main/java/stackpot/stackpot/user/service/UserCommandServiceImpl.java	초기의 potRepository.deleteByUserIdAndPotIds(userId, recruitingPotIds) 중복 호출 제거. 순서는 recruitmentDetail/application/save 삭제 후 최종적으로 potRepository.deleteByUserIdAndPotIds(...) 호출로 정리. 나머지 삭제 로직과 시그니처 변경 없음.

Sequence Diagram(s)

sequenceDiagram
    autonumber
    actor S as UserCommandServiceImpl
    participant RD as RecruitmentDetailRepository
    participant PA as PotApplicationRepository
    participant PS as PotSaveRepository
    participant PR as PotRepository

    Note over S: handleCreatorPotDeletion(userId, recruitingPotIds)

    S->>RD: deleteByPotIds(recruitingPotIds)
    S->>PA: deleteByPotIds(recruitingPotIds)
    S->>PS: deleteByPotIds(recruitingPotIds)
    S->>PR: deleteByUserIdAndPotIds(userId, recruitingPotIds)
    Note right of PR: 중복된 초기 호출 제거됨

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [Refactor][jjaeroong]: 탈퇴 사용자 팟 멤버, 채팅, 댓글 응답 시 새싹 제거하여 반환(#404) #415: 사용자 삭제 흐름에서 동일한 리포지토리 삭제 메서드들을 사용하므로, 본 중복 호출 정리와 직접적으로 연관됨.

Poem

당근을 쥔 토끼가 깡총깡총 뛰며 말하네 🥕
“두 번 지울 필요 없죠, 한 번이면 충분해!”
줄을 맞춰 착착, 지원·스크랩 먼저 비우고,
마지막에 냠—포트 삭제 한 번 콕!
코드 밭엔 바람 솔솔, 버그는 훌훌 날아가네.

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between 29ad779 and 0b9bc11.

📒 Files selected for processing (1)

• src/main/java/stackpot/stackpot/user/service/UserCommandServiceImpl.java (0 hunks)

✨ Finishing Touches

• 📝 Generate Docstrings

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch dev

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.