fix: Merge both properties and allOf in JSON schemas
#78
Conversation
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
Author
|
I have had to patch the NPM package in my codebases with this PR and #73. Would love for both of them to make it into the main package. Happy to take any suggestions to get them over the finish line |
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.
Schemas with both direct
propertiesandallOfwere only generating code for theallOfproperties, completely ignoring direct properties.Example schema that was broken:
{ "type": "object", "required": ["details"], "properties": { "details": { "$ref": "#/components/schemas/Details" } }, "allOf": [ { "$ref": "#/components/schemas/BaseSchema" } ] }