Improve handling of nullable Raw fields for OAS 3.1.0 #961
Conversation
This file contains 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
|
Thanks for contriburing.
Please put editor-specfic stuff in your own global .gitignore.
https://stackoverflow.com/questions/7335420/global-git-ignore
|
|
Sorry about that, I didn't realize a global .gitignore was a thing - thanks for the tip! I've removed the offending section from the |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Modified the implementation of
field2nullablefor OAS 3.1.0 to only append"null"to the list of types if there is already a type for the field. This prevents issues in which a nullable field with no specific associated OAS type can get bound to"type": ["null"], which is overly restrictive.Fixes #960.