회원 탈퇴 기능 구현 - #576
Conversation
|
Warning Review limit reached
Next review available in: 43 minutes Limit details: You’ve used all 1 included review currently available under your plan. You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (5)
Walkthrough회원 탈퇴 메뉴와 2단계 Possibly related PRs
🚥 Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In
`@src/components/layout/SideNavigation/components/Bottom/SideNavigationBottom.tsx`:
- Around line 92-104: Update the 회원 탈퇴 Button in SideNavigationBottom to pass
disabled={isLoggingOut}, preventing it from opening the ACCOUNT_DELETE flow
while logout is in progress.
In `@src/hooks/useDeleteAccount.ts`:
- Around line 17-19: useDeleteAccount의 mutationFn에서
setIntentionalSessionTermination(true)를 제거하고, 탈퇴 성공 시 쿠키 정리 및 이동을 수행하는 onSuccess
흐름 직전에 설정하세요. onError에서는 플래그를 복원하는 대신 삭제 요청의 401/403이 표준
clearInvalidSessionAndRedirect() 경로로 처리되도록 유지하세요.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Repository UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 0979db59-d2c3-49fd-a29c-7d7487a34204
📒 Files selected for processing (16)
e2e/smoke.spec.tspublic/images/account-deleted-background.webpsrc/apis/authApi.tssrc/app/(route)/account-deleted/page.tsxsrc/app/api/member/route.tssrc/app/layout-client.tsxsrc/components/basics/Modal/Modal.tsxsrc/components/layout/SideNavigation/components/Bottom/SideNavigationBottom.tsxsrc/components/wrappers/AccountDeleteModal/AccountDeleteModal.tsxsrc/hooks/useDeleteAccount.tssrc/lib/client/apiClient.tssrc/lib/client/backendClient.tssrc/lib/constants/cookies.tssrc/lib/server/apiClient.tssrc/middleware.tssrc/stores/modalStore.ts
- 탈퇴 안내 및 사유 선택 모달과 백엔드 연동을 추가합니다. - 탈퇴 완료 페이지와 인증 상태 정리 및 접근 제어를 구현합니다. - 401/403 세션 만료 처리와 완료 페이지 리다이렉트 경합을 방지합니다.
- 탈퇴 중 발생한 인증 오류를 보류하고 실패 시 세션 정리 흐름을 복원합니다. - 탈퇴 성공 시 전체 페이지 이동으로 완료 화면과 세션 상태를 확정합니다. - 로그아웃 처리 중 회원 탈퇴 진입을 차단합니다.
8fe18a1 to
2f648fc
Compare
관련 이슈
PR 설명
작업 내용
confirmed,deleteReason, GAclientId를 전달하는 BFF를 추가했습니다.문제 해결
검증
tsc --noEmiteslint .git diff --checkVideo
2026-08-13.12.49.01.mov