fix: match combiner options by ref origins first, then by number of dangerous diffs#73
Merged
Merged
Conversation
…diffs before total diff count
…y pairing Default inlineRefsFlag when callers omit it so normalization always exposes ref metadata for combinersCompareResolver. Prefer oneOf/allOf/anyOf branch pairs that share an inlined $ref, to better align with real-world cases. Adds tests for OpenAPI, AsyncAPI, and JSON Schema
JayLim2
reviewed
May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
fix(compare): match combiner branches by shared $ref before similarity pairing
fix: prioritize combiner candidate matches with fewer breaking/risky diffs before total diff count