Support OpenAPI 3.1. ExclusiveMinimum and ExclusiveMaximum #23
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
charjr
force-pushed
the
fix-3.1
branch
2 times, most recently
from
f4c5575 to
00bc029
Compare
charjr
changed the title
2 tasks
DEVizzent
approved these changes
Nov 19, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
OpenAPI 3.0 had exclusiveMaximum and exclusiveMinimum be boolean values, following the Json schema from 2016.
OpenAPI 3.1 follows the Json Schema from 2020:
exclusiveMaximum MUST be a number
exclusiveMinimum MUST be a number
To support both we need to support those values being numbers as well.
If I haven't solved it in the optimal way let me know. 👍
Handles part of #24