[BUG] 시안 제출 현황 조회 조건 수정#75
Conversation
|
Warning Review limit reached
Next review available in: 54 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. 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.yml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthrough
Changes시안 제출 현황 조회 조건 확장
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Possibly related PRs
Suggested reviewers
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ 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: 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/main/java/ditda/backend/domain/commission/dashboard/repository/DashboardCommissionRepository.java`:
- Line 24: The query in DashboardCommissionRepository is binding a
Set<CommissionStatus> with equality, which is incorrect for multiple statuses.
Update the repository query to use c.status IN :commissionStatuses instead of
c.status = :commissionStatuses, and make sure the method signature and parameter
name match the IN-based lookup so the status filter works correctly.
🪄 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.yml
Review profile: CHILL
Plan: Pro Plus
Run ID: 9172ff00-4b48-4cee-90f8-53b4ee03d507
📒 Files selected for processing (2)
src/main/java/ditda/backend/domain/commission/dashboard/repository/DashboardCommissionRepository.javasrc/main/java/ditda/backend/domain/commission/dashboard/service/InstructorDashboardService.java
Jong0128
left a comment
There was a problem hiding this comment.
바로 머지해도 좋을꺼같습니다!!
수고하셨습니다 👍
🚀 Related issue
Closes #74
#️⃣ Summary
GET /api/v1/instructors/dashboards/draft-submissions)시 시안이 모두 제출된 상태(DRAFT_SELECTING)인 상태의 외주도 포함되도록 수정했습니다.🔧 Changes
📸 Test Evidence
💬 Reviewer Notes
Summary by CodeRabbit
기능 개선
버그 수정