Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Getting an error 'exclusiveMinimum should be number' when setting exclusiveMinimum #86

Open
kobik opened this issue Jul 11, 2021 · 0 comments
Labels
bug Something isn't working

Comments

@kobik
Copy link
Collaborator

kobik commented Jul 11, 2021

It seems that exclusiveMaximum and exclusiveMinimum are not properly supported by the package.

According to OpenApi specs both exclusiveMaximum and exclusiveMinimum should be boolean, but when passing the below property definition it throws an error

      exchange_rate:
        type: number
        format: double
        minimum: 0
        exclusiveMinimum: true
properties['exchange_rate'].exclusiveMinimum should be number

this is because according to the json schema specs exclusiveMaximum and exclusiveMinimum should be passed as a number
https://json-schema.org/understanding-json-schema/reference/numeric.html#range

@kobik kobik added the bug Something isn't working label Jul 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Development

No branches or pull requests

1 participant