[Feature/#377] AI 분석 결과 조직 공유 조회 API 연동 - #391
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes 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: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Plus Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (7)
📝 WalkthroughWalkthrough조직의 최신 공유 AI 리포트를 먼저 조회합니다. 유효한 리포트가 있으면 POST 없이 해당 리포트를 사용합니다. 공유 리포트가 없으면 분석 요청으로 전환합니다. 요약 카드는 조회 상태와 생성 시각을 표시합니다. Changes공유 AI 리포트 흐름
Estimated code review effort: 3 (Moderate) | ~20 minutes Possibly related issues
Possibly related PRs
Suggested labels: Suggested reviewers: Sequence Diagram(s)sequenceDiagram
participant 사용자
participant DashboardAiSummarySection
participant useAiAnalysisReport
participant 조직리포트API
사용자->>DashboardAiSummarySection: 카드 확장
DashboardAiSummarySection->>useAiAnalysisReport: 분석 상태 요청
useAiAnalysisReport->>조직리포트API: 최신 공유 리포트 조회
조직리포트API-->>useAiAnalysisReport: 공유 리포트 또는 없음
alt 유효한 공유 리포트 존재
useAiAnalysisReport-->>DashboardAiSummarySection: 공유 토큰과 생성 시각
else 공유 리포트 없음
DashboardAiSummarySection->>useAiAnalysisReport: POST 분석 요청
end
useAiAnalysisReport-->>DashboardAiSummarySection: 로딩 및 분석 결과 상태
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
📚 Storybook 배포 완료
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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/dashboard/ai-report/components/DashboardAiSummarySection.tsx`:
- Around line 61-73: Prevent the fallback effect in
src/components/dashboard/ai-report/components/DashboardAiSummarySection.tsx:61-73
from calling requestAnalysis when a usable shared report exists, while keeping
hasUsableSharedReport out of that effect’s dependency array. In
src/hooks/dashboard/useAiAnalysisReport.ts:88-105, compute hasUsableSharedReport
from sharedReportListQuery.isSuccess, a non-null latest report, and
latest.status !== "FAILED"; expose it from the hook at
src/hooks/dashboard/useAiAnalysisReport.ts:243-249 and consume it in
DashboardAiSummarySection.tsx:32-41. Add regression coverage verifying
requestAiAnalysis is not called while a usable PENDING or SUCCESS shared report
is being resolved.
🪄 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: Path: .coderabbit.yaml
Review profile: CHILL
Plan: Pro Plus
Run ID: e3f3a3d5-d162-4896-a54c-8bf5cd85d21f
📒 Files selected for processing (2)
src/components/dashboard/ai-report/components/DashboardAiSummarySection.tsxsrc/hooks/dashboard/useAiAnalysisReport.ts
2 participants
🚨 관련 이슈
#377
✨ 변경사항
✏️ 작업 내용
GET /api/ai/organizations/{orgId}/reports연동(대시보드 진입 시 조직 공유 최신 리포트 우선 조회)- 조회 결과 있을 때: POST 없이 해당 accessToken으로 바로 렌더링 (FAILED 건은 채택 안 함)
- 조회 결과 없을 때: 카드 펼침 시 기존 POST → 폴링 플로우로 자동 fallback
분석 기준 2026.06.24 ~ 2026.07.07 · 팀 공유 분석 (2026.07.05))😅 미완성 작업
N/A
📢 논의 사항 및 참고 사항
N/A
스크린샷
Summary by CodeRabbit