Upgrade to OpenAPI 3.1.0 once available

[hspedro]

➕ Enhancement Request

Problem related to enhancement request

Currently, we have a problem that exclusiveMinimum and exclusiveMaximum are defined as numbers in the JSON Schema, but on OpenAPI 3.0 it's still defined as booleans. To solve this, we are writing customization files, but the APIs from the products will keep coming as numbers and updating the type with customization is cumbersome.

On OpenAPI 3.1.0, this seems to be solved, however, kin-openapi only has a roadmap for 3.1.0 and no release. Once available, we should switch to solve exclusiveMinimum and see if anything else brakes.

Related Issues

• exclusiveMinimum and exclusiveMaximum should be boolean fastapi/fastapi#240 (comment)
• JSON Schema Ref with number: https://json-schema.org/understanding-json-schema/reference/numeric.html
• OpenAPI Spec with Boolean instead of number: https://swagger.io/docs/specification/data-models/data-types/

[hspedro]

Blocked by getkin/kin-openapi#230