Skip to content

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

Description

@kobik

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

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions