[refactor] React Query 캐싱 전략 개선#1559
Conversation
- useBanner staleTime/gcTime 24h → 1h (긴급 배너 교체 대응) - usePromotion staleTime 5min → 1min (refetchInterval보다 짧게 조정)
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (4)
Warning
|
✅ UI 변경사항 없음
전체 57개 스토리 · 22개 컴포넌트 |
Summary
useBannerstaleTime/gcTime 24h → 1h (긴급 배너 교체 시 최대 24시간 구버전 노출 리스크 해소)usePromotionstaleTime 5min → 1min (refetchInterval: 3min보다 짧게 조정하여 폴링 후 데이터가 즉시 fresh로 인식되도록 수정)docs/claude/api.md및docs/features/hooks/cacheStrategy.md에 캐싱 전략 기준 문서화Test plan
Closes MOA-863