fix(self-evolving-tools): keep bare object schemas empty#397
Conversation
normalize_schema({"type":"object"}) treated the type key as a property name,
producing properties.type=object. Preserve bare object schemas as
type=object with an empty properties map.
|
Warning Review limit reached
Next review available in: 48 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.yaml Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
bojieli
left a comment
There was a problem hiding this comment.
This fixes the bare-object case by rebuilding every type=object schema from only type, properties, and required. That silently drops valid existing keywords such as description, additionalProperties, and $defs; the previous valid-object path preserved them. Please copy the original object schema and default only the missing properties field, with a regression test that verifies extra schema metadata is retained.
normalize_schema turned {"type":"object"} into a schema with a nested properties type object.
Keep bare object schemas empty.