Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[zod-openapi] - OpenAPI 3.0: invalid exclusiveMinimum / exclusiveMaximum #212

Open
RobbyUitbeijerse opened this issue Jul 1, 2024 · 0 comments

Comments

@RobbyUitbeijerse
Copy link

Hi there!

We just found another small issue with the OpenAPI 3.0 output, here's a diff I shared in the other issue regarding the nullable parsing: https://www.diffchecker.com/Zg4nfCdt/

In OpenAPI 3.0, the exclusiveMinimum is expected to be returned as a boolean, while in 3.1 the property can be a number. Currently, when passing down 3.0 in the patchNestjsSwagger, the

expected

"exclusiveMinimum": true,

What we receive (which is correct in 3.1, but invalid in 3.0)

"exclusiveMinimum": 0
@RobbyUitbeijerse RobbyUitbeijerse changed the title [zod-openapi] OpenAPI 3.0: invalid exclusiveMinimum / exclusiveMaximum [zod-openapi] 0 OpenAPI 3.0: invalid exclusiveMinimum / exclusiveMaximum Jul 1, 2024
@RobbyUitbeijerse RobbyUitbeijerse changed the title [zod-openapi] 0 OpenAPI 3.0: invalid exclusiveMinimum / exclusiveMaximum [zod-openapi] - OpenAPI 3.0: invalid exclusiveMinimum / exclusiveMaximum Jul 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant