Convert nullable one ofs #34
Open
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
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.
The pull request goal is to fix an edge case of the down conversion where orphan
oneOf([{ "type": "null" }, {..}]would be converted tooneOf([{ "nullable": true }, {..}].This is invalid because nullable must have a sibling
typefield.This PR adds the
type.If the
typeisarray. It also inlines the array type, becausetype: arrayare required to have a siblingitemsobject.Please refer to the tests cases added to understand the change with detail.
The conversion result was tested with spotlight spectral, and the results look good on other files of a much larger project.