This repository was archived by the owner on Nov 8, 2024. It is now read-only.
Include nullable with Schema Object without a type on OAS 3.1 #599
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
kylef
force-pushed
the
kylef/type-array
branch
from
89573a5 to
cd9b4c0
Compare
kylef
force-pushed
the
kylef/type-array
branch
from
cd9b4c0 to
2c25d70
Compare
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.
In OpenAPI 3.1,
nullis permitted intype. This causes the behaviour when you have a schema without a type restriction to allow null. This wasn't the case in OpenAPI 3.0 or older, because these version removesnullfrom JSON Schema's type system.