feat: add partial SIDC decomposition - #21
Conversation
|
Warning Review limit reached
More reviews will be available in 3 minutes and 42 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 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 configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
@codex review |
|
@greptileai review |
Summary
explainSidcwith a curated/partial result union and explicit per-field coverage.milsymbolmetadata plus the existing curated function-ID labels.Validation
npm testnpm pack --dry-runScope limits
unknownFields.milsymbolrenderability.Greptile Summary
This PR expands SIDC explanation beyond the curated fixture set. The main changes are:
unknownFieldsin explain results.Confidence Score: 5/5
The SIDC explanation paths exercised by the package contract behave as described.
No code issues were identified in the finalized review. Runtime validation showed the intended base-to-head behavior change for partial decomposition, unknown field reporting, invalid and unsupported handling, and the requested package validation commands completed successfully.
None.
What T-Rex did
Reviews (2): Last reviewed commit: "fix: tighten partial SIDC coverage" | Re-trigger Greptile