Bugfix/exclusive properties dont allow booleans for open api 3.1 #5993
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 generated open api spec is currently invalid for open api 3.1.
exclusiveMinimum and exclusiveMaximum are still used as boolean, while properties minimum and exclusiveMinimum are merged into one property exclusiveMinimum.
See https://www.openapis.org/blog/2021/02/16/migrating-from-openapi-3-0-to-3-1-0
The only problem I see now, is that users can configure their open api version.
But I don't know how I can toggle the logic between 3.0 and 3.1.
Any help is appreciated. Thx!