search

swagger-api / swagger-editor

Swagger Editor
https://editor.swagger.io
Apache License 2.0
8.96k stars 2.26k forks source link

Wrong exclusiveMinimum/exclusiveMaximum validation in OpenApi 3.0.3 #4545

Open RastislavGraus opened 1 year ago

RastislavGraus commented 1 year ago

Q&A (please complete the following information)

Content & configuration

Open public Swagger-Editor on URI https://editor-next.swagger.io/ and paste my OpenApi definition in it.

Example Swagger/OpenAPI definition: openapi: 3.0.3 info: description: Wrong validation title: Validation version: 1.0.0 paths: components: schemas: Data: properties: quantity: type: number minimum: 0.000 exclusiveMinimum: true type: object

Swagger-Editor configuration options: default

Describe the bug you're encountering

After paste of given OpenApi definition, you get a wrong validation error: "14 | 10017 | exclusiveMinimum' value must be a number". According to documentation https://swagger.io/docs/specification/data-models/data-types/#numbers is my definition correct.

To reproduce...

Steps to reproduce the behavior:

  1. Go to 'https://editor-next.swagger.io/'
  2. Paste given definition (yaml)
  3. See error

Expected behavior

No validation error will be displayed

Screenshots

Additional context or thoughts

mdaneri commented 11 months ago

In openapi 3.0.x eclusiveMinimum and exclusiveMaximus must be a number With openapi 3.1 both are booleans