refactor: 아카이브 탭별 데이터 로딩 분리 및 위시 플로우 개선

[iOdiO89]

요약

아카이브 진입 시 활성 탭과 무관하게 위시·토너먼트 기록을 모두 prefetch하던 구조를 탭 단위 컴포넌트로 분리해, 보고 있는 탭의 데이터만 서버에서 가져오도록 변경했습니다. 홈도 토너먼트 목록 범위로만 await를 두어 첫 화면 TTFB를 줄였고, 이미지 로딩 중 빈 화면이 보이던 문제를 skeleton으로 처리했습니다. layout·상세 페이지의 권한 검증은 fetchQuery로 단순화해 getMe 중복 호출을 방지했습니다.

변경 사항

1. 아카이브 — 탭별 데이터 로딩 분리

• 기존: archive/page.tsx에서 활성 탭과 관계없이 위시 infinite query + 토너먼트 목록 prefetch를 모두 await
• 변경: wish-content/, tournament-history-content/(index.tsx + client.tsx)로 분리해 활성 탭만 mount·prefetch
• WishlistContent / TournamentHistoryContent 제거 → WishlistList / TournamentHistoryList + WishCardSkeleton 도입
• 아카이브 페이지 props 네이밍 정리 (WishlistPage → ArchivePage)

2. 홈 — 토너먼트 목록 await 범위 축소

• 기존: home/page.tsx 전체가 async이며 진입 시 토너먼트 목록 prefetch를 await
• 변경: tournament-list/ 서버 컴포넌트로 분리, 해당 섹션만 prefetch·hydrate
• 홈 레이아웃(헤더·FAB 등)은 즉시 렌더되고 토너먼트 목록만 별도 스트리밍

3. 이미지 로딩 UX — BaseImage·Skeleton

• BaseImage loading → success 전환 시점에 아무것도 표시되지 않던 현상 수정
• WishCard 이미지 로딩 시 Skeleton 적용
• UserProfile 이미지 로딩 시 Skeleton 적용

4. 권한 검증 — fetchQuery 단순화

• 기존: prefetch + getQueryState로 권한 검증
• 변경: fetchQuery(['me']) 단일 호출로 단순화 (archive/wish/[id]/page.tsx)
• archive / login / mypage·withdraw layout에서 fetchQuery + HydrationBoundary 적용 → layout·page 간 getMe 중복 호출 방지
• getMe 404 시 SESSION_EXPIRED 쿼리와 함께 로그인 페이지로 redirect

5. 위시 — 삭제 토스트

• 위시 단일 삭제 시 삭제 성공 토스트 추가

스크린샷

아카이브 위시 탭 lighthouse LCP 지표 점수를 3차례에 걸쳐 개선했습니다. 이미지 로드와 관련하여 추가 개선이 필요해보입니다.

기존

2026-06-24.3.28.56.mov

개선 이후

2026-06-24.3.28.14.mov

연관 이슈

closes #261

Summary by CodeRabbit

• New Features
  • 아카이브 화면이 위시리스트/토너먼트 기록 중심의 새 구성으로 정리되어 로딩과 전환이 매끄러워졌습니다.
  • 위시 카드 로딩 스켈레톤과, 위시 편집 화면의 “처리 실패” 상태에서 삭제 버튼이 추가되었습니다.
  • 일부 이미지를 더 빠르게 불러오도록 미리 로딩(preload) 흐름을 확장했습니다.
• Bug Fixes
  • 비어 있는 목록에서 안내 문구/하단 탭 표시가 더 일관되게 동작합니다.
  • 이미지 표시 중 에러/전환 UI가 안정적으로 처리됩니다.
• Performance / UI Improvements
  • 프로필 이미지 렌더링을 개선하고, 로딩 스피너는 지연 로딩 방식으로 전환했습니다.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
depromeet	Ready	Preview, Comment	Jun 26, 2026 12:23pm

[coderabbitai]

Warning

Review limit reached

@iOdiO89, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 23 minutes and 15 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

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 credits.

🚦 How do rate 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Repository UI

Review profile: CHILL

Plan: Pro

Run ID: 062762f8-02f8-488b-b934-dc0e69e0ab2d

📥 Commits

Reviewing files that changed from the base of the PR and between 8e0a010 and 997432e.

📒 Files selected for processing (8)

• apps/app/app/index.tsx
• apps/web/src/app/archive/_components/wish-content/client.tsx
• apps/web/src/app/archive/wish/[id]/_components/ItemEditForm.tsx
• apps/web/src/app/archive/wish/[id]/layout.tsx
• apps/web/src/app/tournament/[id]/create/_components/tournament-header/TournamentHeader.tsx
• apps/web/src/components/header/index.tsx
• apps/web/src/components/status-chip/statusChip.style.ts
• apps/web/src/components/tournament-card/index.tsx

📝 Walkthrough

Walkthrough

Archive, Home, Login, MyPage 레이아웃의 React Query 하이드레이션 흐름이 정리되고, 위시/토너먼트 콘텐츠가 서버·클라이언트 분리 구조로 재구성되며, 이미지 로딩 힌트가 priority에서 preload로 바뀌었습니다.

Changes

Archive/Home 비차단 prefetch 재편 및 콘텐츠 구조 변경

Layer / File(s)	Summary
QueryClient SSR 메모이제이션 및 BaseImage preload 계약 apps/web/src/utils/queryClient.ts, apps/web/src/components/base-image/index.tsx, apps/web/src/components/button/index.tsx, apps/web/src/components/user-profile-group/index.tsx	getQueryClient 서버 경로가 cache(makeQueryClient)로 메모이제이션되고, BaseImage에 preload/unoptimized 기본값과 srcKey 기반 상태 동기화가 추가된다. UserProfileGroup은 BaseImage와 Skeleton으로 바뀌고, Button의 Spinner는 동적 로딩으로 전환된다.
Archive/Login/MyPage 레이아웃 인증 흐름 전환 apps/web/src/app/archive/layout.tsx, apps/web/src/app/login/layout.tsx, apps/web/src/app/mypage/withdraw/layout.tsx	getMe() 직접 호출을 queryClient.fetchQuery(['me'], getMe)로 교체하고, 401/404 에러 시 SESSION_EXPIRED를 포함한 로그인 리다이렉트로 분기한다. 반환값을 HydrationBoundary(dehydrate(queryClient))로 감싸 me 쿼리 상태를 하이드레이션한다.
Home 토너먼트 목록 서버/클라이언트 분리 apps/web/src/app/home/_components/tournament-list/index.tsx, apps/web/src/app/home/_components/tournament-list/client.tsx, apps/web/src/app/home/page.tsx	HomePage에서 async/prefetch/HydrationBoundary 로직을 제거하고, TournamentList 서버 컴포넌트가 prefetchQuery+HydrationBoundary를 담당한다. TournamentListClient가 statuses prop을 받아 useGetTournamentList를 호출하도록 재편된다.
Archive 페이지 탭 라우팅 단순화 apps/web/src/app/archive/page.tsx	WishlistPage가 ArchivePage로 교체되면서 페이지 레벨의 prefetchInfiniteQuery/prefetchQuery/Suspense/WishlistSkeleton 로직이 제거되고, activeTab 값에 따라 WishContent 또는 TournamentHistoryContent를 조건 렌더링하는 구조로 변경된다.
WishContent 서버/클라이언트 분리 및 WishlistList 구성 apps/web/src/app/archive/_components/wish-content/index.tsx, apps/web/src/app/archive/_components/wish-content/client.tsx, apps/web/src/app/archive/_components/WishlistList.tsx, apps/web/src/app/archive/_components/WishCardSkeleton.tsx, apps/web/src/app/archive/_components/WishlistTabContent.tsx	WishlistContent가 제거되고, WishContent 서버 컴포넌트가 prefetchInfiniteQuery와 HydrationBoundary로 데이터를 준비한다. WishContentClient가 useWishlistDelete, useShareIntentWish, WishlistList, WishlistBottomBar, WishlistFabArea, WishAddDialog를 연결하며, WishlistList는 무한 스크롤과 SSE 폴백을 담당한다. WishCardSkeleton이 추가되고 WishlistTabContent의 빈 상태 래퍼가 main에서 div로 바뀐다.
TournamentHistoryContent 서버/클라이언트 분리 및 TournamentHistoryList 구성 apps/web/src/app/archive/_components/tournament-history-content/index.tsx, apps/web/src/app/archive/_components/tournament-history-content/client.tsx, apps/web/src/app/archive/_components/TournamentHistoryList.tsx	기존 TournamentHistoryContent 단일 컴포넌트가 제거되고, 서버 index.tsx가 prefetchQuery+HydrationBoundary를 담당하며, client.tsx가 TournamentHistoryList와 BottomTabBar를 렌더링한다. TournamentHistoryList는 빈 상태 UI와 TournamentCard 목록을 전환 렌더링한다.
위시 편집 에러 처리를 layout으로 이동 apps/web/src/app/archive/wish/[id]/layout.tsx, apps/web/src/app/archive/wish/[id]/page.tsx, apps/web/src/app/archive/wish/[id]/_components/ItemEditForm.tsx	WishEditLayout이 위시 단건 조회, React Query 캐시 세팅, `PROCESSING
WishCard/WishGrid BaseImage 전환 및 preload 적용 apps/web/src/app/archive/_components/wish-grid/WishCard.tsx, apps/web/src/app/archive/_components/wish-grid/index.tsx, apps/web/src/app/tournament/[id]/match/_components/FinalProductCard.tsx, apps/web/src/app/tournament/[id]/match/_components/ProductCard.tsx, apps/web/src/app/tournament/[id]/result/_components/ReceiptDrawMachine.tsx, apps/web/src/app/mypage/withdraw/page.tsx, apps/web/src/app/tournament/[id]/create/_components/tournament-item-basket/TournamentBasketItem.tsx, apps/web/src/app/tournament/[id]/create/_components/tournament-header/TournamentHeader.tsx, apps/web/src/consts/zIndex.ts	WishCard가 BaseImage로 교체되고 preload prop이 추가된다. WishGrid는 앞 4개 항목에만 preload를 전달하도록 바뀌며, FinalProductCard, ProductCard, ReceiptDrawMachine, MyPage 탈퇴 페이지와 TournamentBasketItem은 priority를 preload로 바꾸고 z-index를 Z_INDEX.BASE_IMAGE + 10으로 맞춘다. Z_INDEX.BASE_IMAGE 상수가 추가된다.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

• depromeet/PIKI-Client#196: apps/web/src/app/tournament/[id]/result/_components/ReceiptDrawMachine.tsx의 이미지 로딩 힌트 변경과 같은 컴포넌트 경로를 수정합니다.
• depromeet/PIKI-Client#161: archive/layout.tsx의 getMe() 기반 권한 처리와 React Query 하이드레이션 흐름을 다룹니다.

Suggested reviewers

• ychany
• kanghaeun

🚥 Pre-merge checks | ✅ 2 | ❌ 3

❌ Failed checks (3 warnings)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	위시 탭 분리는 보이지만 CRUD 캐시 정리와 shell-first 상세 진입, 첫 화면 스켈레톤 노출 같은 핵심 요구가 충분히 확인되지 않습니다.	위시 생성/수정/삭제/재파싱 훅의 targeted cache update와 rollback, 상세 페이지 shell-first 렌더, archive 첫 화면 스켈레톤을 보완하세요.
Out of Scope Changes check	⚠️ Warning	홈 페이지, 로그인/마이페이지 레이아웃, 토너먼트·공통 이미지 컴포넌트 등 위시 탭 외 변경이 다수 포함돼 범위를 넘어섭니다.	위시 탭/상세/CRUD 관련 변경만 남기고 홈, 공통 이미지, 기타 레이아웃 리팩터링은 별도 PR로 분리하세요.
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목이 아카이브 탭 로딩 분리와 위시 플로우 개선이라는 핵심 변경을 정확히 요약합니다.

---

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

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 6

🧹 Nitpick comments (3)

apps/web/src/app/home/_components/tournament-list/client.tsx (1)

7-9: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

Props 타입명을 TournamentListClientProps로 변경하세요.

코딩 가이드라인 및 팀 컨벤션상 컴포넌트 props 타입은 {ComponentName}Props 패턴을 따라야 합니다. 일반 Props 대신 TournamentListClientProps를 사용해 주세요.

♻️ 제안 변경

-type Props = {
+type TournamentListClientProps = {
   statuses: TournamentStatusT[];
 };

-function TournamentListClient({ statuses }: Props) {
+function TournamentListClient({ statuses }: TournamentListClientProps) {

As per coding guidelines: "Props type names must follow pattern {ComponentName}Props".

🤖 Prompt for 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.

In `@apps/web/src/app/home/_components/tournament-list/client.tsx` around lines 7
- 9, Rename the generic Props type used by TournamentListClient to
TournamentListClientProps to match the component props naming convention. Update
the type alias in the TournamentListClient component and any related references
so the component’s props follow the {ComponentName}Props pattern consistently.

Sources: Coding guidelines, Learnings

apps/web/src/app/mypage/withdraw/layout.tsx (1)

25-25: 📐 Maintainability & Code Quality | 🔵 Trivial | 💤 Low value

비-MEMBER 리다이렉트 목적지가 archive 레이아웃과 다릅니다.

여기서는 redirect(ROUTES.LOGIN)로 보내지만 archive/layout.tsx는 getLoginPath(redirectPath)로 redirect 쿼리를 보존합니다. 일관성을 위해 redirectPath를 살리는 방식이 의도된 것인지 확인해 주세요.

🤖 Prompt for 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.

In `@apps/web/src/app/mypage/withdraw/layout.tsx` at line 25, The redirect in the
withdraw layout is inconsistent with the archive layout because it drops the
intended return path. Update the MEMBER guard in the withdraw layout to use the
same login-path flow as archive layout by preserving the current destination via
a redirectPath when calling the login redirect helper, and verify the behavior
matches the existing getLoginPath(redirectPath) usage rather than redirecting
directly to ROUTES.LOGIN.

apps/web/src/app/archive/_components/wish-grid/index.tsx (1)

56-61: 🚀 Performance & Scalability | 🔵 Trivial | 💤 Low value

상위 4개 이미지 동시 preload는 LCP에 역효과일 수 있습니다.

Next.js 16에서 preload는 <head>에 <link rel="preload">를 주입합니다. 여러 이미지를 동시에 preload하면 critical CSS/JS와 대역폭 경쟁이 발생해 오히려 LCP/FCP가 나빠질 수 있습니다. 실제 LCP 후보(보통 1장)에만 preload를 적용하고, 나머지 above-the-fold 항목은 loading="eager"/fetchPriority="high"로 두는 방식을 검토해 보세요.

🤖 Prompt for 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.

In `@apps/web/src/app/archive/_components/wish-grid/index.tsx` around lines 56 -
61, The WishCard image loading logic in wish-grid/index.tsx currently preloads
the first 4 images, which can hurt LCP/FCP by competing with critical resources.
Update the mapping logic that sets the WishCard preload prop so only the single
likely LCP candidate gets preload, and let other above-the-fold images use eager
loading or high fetch priority instead. Keep the fix localized to the WishCard
usage in the grid component and adjust any related image props accordingly.

🤖 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 `@apps/web/src/app/archive/_components/wish-content/client.tsx`:
- Around line 27-33: The empty-state path in WishlistList/WishlistTabContent is
rendering a second <main> inside the wrapper <main> in client.tsx. Update
WishlistTabContent’s empty-state container to a non-main element, or keep only
one <main> in the WishlistList tree so the document has a single main landmark.

In `@apps/web/src/app/archive/layout.tsx`:
- Around line 28-33: The archive layout error handling in the catch block only
redirects on 404 and lets other axios failures from getMe fall through, which
can bypass the MEMBER-only guard. Update the catch logic in archive/layout.tsx
to handle non-404 axios errors explicitly: use
isAxiosError<ApiErrorResponseT>(error) to branch, keep the existing 404 redirect
behavior, and for 401/403/500 and other non-404 responses either redirect to the
login path with QUERY_ACTION.VALUE.SESSION_EXPIRED or rethrow so
HydrationBoundary does not proceed on failed auth.

In `@apps/web/src/app/archive/wish/`[id]/_components/ItemEditForm.tsx:
- Line 4: The delete success toast is duplicated between ItemEditForm’s
handleDelete per-call onSuccess and the useDeleteWish hook. Update handleDelete
to only call deleteWishMutation() without passing a per-call onSuccess, and
remove the unused toast import from ItemEditForm so the success toast is shown
only inside useDeleteWish.

In `@apps/web/src/app/archive/wish/`[id]/page.tsx:
- Around line 36-39: The catch block in the archive wish page only handles the
404 case, so 403 responses still fall through to throw and can hit the error
screen. Update the error handling in the page component’s catch path to preserve
the existing 403 routing behavior alongside the 404 redirect, using the same
redirect logic already present in this flow. Keep the decision inside the
archive wish page handler so both “not found” and “forbidden” responses are
routed correctly before rethrowing anything else.

In `@apps/web/src/app/mypage/withdraw/layout.tsx`:
- Around line 26-31: The catch block in MyPageMemberOnlyLayout only handles
Axios 404s, so other Axios errors are swallowed and can still allow children to
render before auth is confirmed. Update the error handling in the layout logic
around isAxiosError and redirect/getLoginPath so that non-404 Axios errors also
trigger the same fallback behavior as archive/layout.tsx, instead of being
ignored.

In `@apps/web/src/utils/queryClient.ts`:
- Line 21: The server-side path in getQueryClient currently creates a new cached
wrapper every time by calling cache(makeQueryClient) inline, which prevents
request-local memoization from being shared. Move cache(makeQueryClient) to
module scope in queryClient.ts, reuse that single memoized function inside
getQueryClient, and keep makeQueryClient as the underlying factory so server
requests consistently share the same cache.

---

Nitpick comments:
In `@apps/web/src/app/archive/_components/wish-grid/index.tsx`:
- Around line 56-61: The WishCard image loading logic in wish-grid/index.tsx
currently preloads the first 4 images, which can hurt LCP/FCP by competing with
critical resources. Update the mapping logic that sets the WishCard preload prop
so only the single likely LCP candidate gets preload, and let other
above-the-fold images use eager loading or high fetch priority instead. Keep the
fix localized to the WishCard usage in the grid component and adjust any related
image props accordingly.

In `@apps/web/src/app/home/_components/tournament-list/client.tsx`:
- Around line 7-9: Rename the generic Props type used by TournamentListClient to
TournamentListClientProps to match the component props naming convention. Update
the type alias in the TournamentListClient component and any related references
so the component’s props follow the {ComponentName}Props pattern consistently.

In `@apps/web/src/app/mypage/withdraw/layout.tsx`:
- Line 25: The redirect in the withdraw layout is inconsistent with the archive
layout because it drops the intended return path. Update the MEMBER guard in the
withdraw layout to use the same login-path flow as archive layout by preserving
the current destination via a redirectPath when calling the login redirect
helper, and verify the behavior matches the existing getLoginPath(redirectPath)
usage rather than redirecting directly to ROUTES.LOGIN.

🪄 Autofix (Beta)

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

Run ID: a641890e-6c3a-4576-b462-4620bc6defdc

📥 Commits

Reviewing files that changed from the base of the PR and between 69d903e and bd7ae74.

📒 Files selected for processing (31)

• apps/web/src/app/archive/_components/TournamentHistoryContent.tsx
• apps/web/src/app/archive/_components/TournamentHistoryList.tsx
• apps/web/src/app/archive/_components/WishCardSkeleton.tsx
• apps/web/src/app/archive/_components/WishlistContent.tsx
• apps/web/src/app/archive/_components/WishlistList.tsx
• apps/web/src/app/archive/_components/WishlistSkeleton.tsx
• apps/web/src/app/archive/_components/WishlistTabContent.tsx
• apps/web/src/app/archive/_components/tournament-history-content/client.tsx
• apps/web/src/app/archive/_components/tournament-history-content/index.tsx
• apps/web/src/app/archive/_components/wish-content/client.tsx
• apps/web/src/app/archive/_components/wish-content/index.tsx
• apps/web/src/app/archive/_components/wish-grid/WishCard.tsx
• apps/web/src/app/archive/_components/wish-grid/index.tsx
• apps/web/src/app/archive/layout.tsx
• apps/web/src/app/archive/page.tsx
• apps/web/src/app/archive/wish/[id]/_components/ItemEditForm.tsx
• apps/web/src/app/archive/wish/[id]/page.tsx
• apps/web/src/app/home/_components/tournament-list/client.tsx
• apps/web/src/app/home/_components/tournament-list/index.tsx
• apps/web/src/app/home/page.tsx
• apps/web/src/app/login/layout.tsx
• apps/web/src/app/mypage/withdraw/layout.tsx
• apps/web/src/app/mypage/withdraw/page.tsx
• apps/web/src/app/tournament/[id]/match/_components/FinalProductCard.tsx
• apps/web/src/app/tournament/[id]/match/_components/ProductCard.tsx
• apps/web/src/app/tournament/[id]/result/_components/ReceiptDrawMachine.tsx
• apps/web/src/components/base-image/index.tsx
• apps/web/src/components/button/index.tsx
• apps/web/src/components/user-profile-group/index.tsx
• apps/web/src/utils/queryClient.ts
• eas.json

💤 Files with no reviewable changes (4)

• apps/web/src/app/archive/_components/WishlistSkeleton.tsx
• eas.json
• apps/web/src/app/archive/_components/TournamentHistoryContent.tsx
• apps/web/src/app/archive/_components/WishlistContent.tsx

[coderabbitai]

Actionable comments posted: 1

🧹 Nitpick comments (1)

apps/web/src/app/archive/wish/[id]/layout.tsx (1)

12-12: 📐 Maintainability & Code Quality | 🔵 Trivial | ⚡ Quick win

상대 경로 대신 @/* 절대 alias를 사용해 주세요.

새 파일의 import도 프로젝트 import 규칙에 맞춰 absolute group에 포함하는 편이 좋습니다.

수정 예시

+import { getWish } from '`@/app/archive/wish/`[id]/_apis/getWish';
 import { ROUTES } from '`@/consts/route`';
 import type { ApiErrorResponseT } from '`@/types/api`';
 import { getLoginPath } from '`@/utils/loginRedirect`';
 import { parseIdParam } from '`@/utils/parseIdParam`';
 import { getQueryClient } from '`@/utils/queryClient`';
-
-import { getWish } from './_apis/getWish';

As per coding guidelines, apps/web/src/**/*.{ts,tsx}: Use absolute path alias @/* for imports instead of relative paths.

🤖 Prompt for 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.

In `@apps/web/src/app/archive/wish/`[id]/layout.tsx at line 12, The import in the
layout file uses a relative path instead of the project’s required `@/*`
absolute alias. Update the `getWish` import in `layout.tsx` to use the absolute
import style, and keep it in the absolute import group so it matches the repo’s
`apps/web/src/**/*.{ts,tsx}` import convention.

Source: Coding guidelines

🤖 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 `@apps/web/src/app/archive/wish/`[id]/layout.tsx:
- Around line 20-22: The archive wish layout is treating a 403 from getWish as
if it should trigger a login redirect, but /archive/** is already protected by
the parent archive layout. Update the redirect handling in layout.tsx so only
404s are routed back to the archive page, and leave 403s to the existing
authorization flow or separate resource-policy handling instead of sending users
to login. Use the getWish and redirectPath logic in the archive/[id]/layout.tsx
path to remove any per-page guest/session assumptions.

---

Nitpick comments:
In `@apps/web/src/app/archive/wish/`[id]/layout.tsx:
- Line 12: The import in the layout file uses a relative path instead of the
project’s required `@/*` absolute alias. Update the `getWish` import in
`layout.tsx` to use the absolute import style, and keep it in the absolute
import group so it matches the repo’s `apps/web/src/**/*.{ts,tsx}` import
convention.

🪄 Autofix (Beta)

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

Run ID: 4b0593fb-5ddb-409a-b7ee-915bdcac9097

📥 Commits

Reviewing files that changed from the base of the PR and between bd7ae74 and 4d80cd3.

📒 Files selected for processing (6)

• apps/web/src/app/archive/_components/WishlistTabContent.tsx
• apps/web/src/app/archive/layout.tsx
• apps/web/src/app/archive/wish/[id]/layout.tsx
• apps/web/src/app/archive/wish/[id]/page.tsx
• apps/web/src/app/mypage/withdraw/layout.tsx
• apps/web/src/utils/queryClient.ts

🚧 Files skipped from review as they are similar to previous changes (4)

• apps/web/src/app/archive/_components/WishlistTabContent.tsx
• apps/web/src/utils/queryClient.ts
• apps/web/src/app/archive/layout.tsx
• apps/web/src/app/mypage/withdraw/layout.tsx

[coderabbitai]

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 `@apps/web/src/app/archive/wish/`[id]/_components/ItemEditForm.tsx:
- Around line 141-151: The delete action in ItemEditForm is still enabled during
an in-flight save, which allows PATCH and DELETE to race on the same wish.
Update the Delete button’s disabled/loading gating and the handleDelete path to
also respect isPatchWishPending, alongside the existing isDeleteWishPending and
isPostWishRefreshPending checks, so deletion cannot start while a save is
pending.

In
`@apps/web/src/app/tournament/`[id]/create/_components/tournament-header/TournamentHeader.tsx:
- Line 39: The central `Header` container is receiving `line-clamp-1`, which
conflicts with its existing `flex items-center justify-center` layout in
`TournamentHeader` and `Header`. Move the truncation behavior off the center
wrapper and apply it to the actual title text element instead, or add a
dedicated title slot/class to `Header` for clamping. Update `TournamentHeader`
so the center container only handles layout, while the text node handles the
single-line ellipsis styling.

🪄 Autofix (Beta)

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

Run ID: 23307523-de37-467e-a09e-d27d420577ec

📥 Commits

Reviewing files that changed from the base of the PR and between 4d80cd3 and 8e0a010.

📒 Files selected for processing (8)

• apps/app/app/index.tsx
• apps/web/src/app/archive/wish/[id]/_components/ItemEditForm.tsx
• apps/web/src/app/tournament/[id]/create/_components/tournament-header/TournamentHeader.tsx
• apps/web/src/app/tournament/[id]/create/_components/tournament-item-basket/TournamentBasketItem.tsx
• apps/web/src/app/tournament/[id]/match/_components/FinalProductCard.tsx
• apps/web/src/app/tournament/[id]/match/_components/ProductCard.tsx
• apps/web/src/components/base-image/index.tsx
• apps/web/src/consts/zIndex.ts

🚧 Files skipped from review as they are similar to previous changes (3)

• apps/web/src/app/tournament/[id]/match/_components/ProductCard.tsx
• apps/web/src/app/tournament/[id]/match/_components/FinalProductCard.tsx
• apps/web/src/components/base-image/index.tsx