[BUG] exclusiveMinimum and exclusiveMaximum should be boolean

Describe the bug exclusiveMinimum and exclusiveMaximum should be of type boolean

To Reproduce A field with greater than property is generated as:

end:
    exclusiveMinimum: 0.0
    type: number

Expected behavior

It should be:

end:
    exclusiveMinimum: true
    minimum: 0.0
    type: number

Environment:

• OS: Linux and macOS
• FastAPI version 0.22.0
• Python version 3.7

Additional context According to OpenAPI, these fields should be boolean as listed here.

[domiko96]

Is there already a way to generate an OpenAPI 3.1 json, that can be imported into https://editor.swagger.io/, so one can generate a client from the fastAPI without having to fix this problems manually?

[Hultner]

I’ve also run into this and did some heavy investigation into it in collaboration with @Stranger6667 yesterday to make sure that it’s indeed a bug in FastAPI/pydantic and not schemathesis. Was going to post it as an issue here but now I see that there already is one.

From our investigations it was clear that the spec for OpenAPI 3.0.x which uses draft 4/json-schema-00 is to use an integer for exclusiveM… and not a boolean combined with minimum/maximum. However, the next version which is still WIP (OAS v3.1.0) will use the newer JSON-Schema version and be compliant with current behaviour. So it would probably be wise to keep the current behaviour behind a feature toggle or similar for when that is live.

References

• Reference to draft-4 in OpenApi 2: https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v2.0/schema.json#L972
• OpenApi v3 specification using boolean value for exclusiveMinimum/maximum https://github.com/OAI/OpenAPI-Specification/blob/master/schemas/v3.0/schema.json#L356
• https://swagger.io/docs/specification/data-models/data-types/
• http://spec.openapis.org/oas/v3.0.3#schema-object
• http://spec.openapis.org/oas/v3.0.3#data-types