You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
The text was updated successfully, but these errors were encountered:
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 thepatchNestjsSwagger
, theexpected
What we receive (which is correct in 3.1, but invalid in 3.0)
The text was updated successfully, but these errors were encountered: