Repository navigation
fix: retain allOf intersections without changing flat parameter views - #382
Merged
Merged
Conversation
I adapt primitive allOf only beside anyOf or oneOf and keep the existing flat path for allOf-only parameters. Composed schemas retain default and nullable values, and allOf branch format annotations stay out of the mapping. Existing anyOf and oneOf branch formats remain unchanged. I added fail-first tests for intersection constraints and the old flat allOf enum/default and nullable views.
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 join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Closes #381
I adapt primitive allOf only beside anyOf or oneOf, and keep the existing flat path for allOf-only parameters. Composed schemas keep default and nullable, and allOf branch formats stay out of the mapping.
Tests are fail-first, and tsc and the full suite pass.