Specification OpenAPI - Field (exclusiveMinimum, exclusiveMaximum)

[carlos-rian]

Spec Bug

I'm creating my documentation using "FastAPI". I'm having trouble importing the generated schema into Azure API Management. Because when I use the "gt" argument in the "Query" object, it defines the exclusiveMinimum field, in the OpenAPI documentation, this field is a boolean, but in FastAPI it is defined with Integer!

Spec OpenAPI:

• https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v3.0/schema.yaml
  
• https://datatracker.ietf.org/doc/html/draft-wright-json-schema-validation-00#page-6
  

Schema OpenAPI FastAPI

FastAPI Query

FastAPI Docs

[juanbeniteza]

I found this is a Pydantic issue.

It seems it depends on the version of JSONSchema the OpenAPI is targeting.

[carlos-rian]

@JuanBenitezDev I understand, but I found that Spec OpenAPI V2 is also Boolean.

https://github.com/OAI/OpenAPI-Specification/blob/main/schemas/v2.0/schema.json
http://json-schema.org/draft-04/schema#

[juanbeniteza]

@carlos-rian Yeah I know, but Pydantic is generating schemas that are compliant with the last versions of the specifications. You can see that here

The last version of OpenAPI at the time I'm writing this is 3.1. This new version is based on the JSON Schema Draft 2020-12, here the exclusiveMinimum and exclusiveMaximum are numbers, you can see them here

You can even check what are the things changing from OpenAPI v3 to v3.1 here

My guess is that Azure API Management is expecting a specific OpenAPI version.

[Alexander-N]

See #240 for more discussion. As workaround you could use ge instead of gt, e.g.

Query(..., ge=11)

instead of

Query(..., gt=10)

[carlos-rian]

@JuanBenitezDev I understand, it´s makes sense. Thanks you!

Hi @Alexander-N. Yes. I've seen some discussions about this. I solved the problem using ge. But I thought it was a bug in Pydantic. Thanks!