exclusiveMinimum
/exclusiveMaximum
OAS v3 is not validated correctly
#36
Labels
question
Further information is requested
What happened?
When using
exclusiveMinimum
andexclusiveMaximum
properties with OAS v3, the validator marks its usage as an error, saying its value should be a boolean. However, since OAS v3 this field now holds the actual (exclusive) minimum/maximum value, and is no longer a boolean.What should have happened instead?
An integer or float should be accepted as the value for
exclusiveMinimum
/exclusiveMaximum
. A boolean should no longer be accepted when using OAS v3.x.x.Minimal reproducible OpenAPI snippet
Screenshots
Additional context
Using OAS 3.0.2.
The text was updated successfully, but these errors were encountered: