Closed cornerman closed 9 months ago
Sorry, I mixed up something in my configuration. It actually works correct now.
Sorry for the confusion, I have updated the description. It was the other way around. In sttp-apispec 0.7.1
, we get type: "null"
, which is not valid in openapi 3.0.3
(according to https://swagger.io/docs/specification/data-models/data-types/).
Now, I understand that this is actually coming from tapir
. I opened a PR there: https://github.com/softwaremill/tapir/pull/3331
When updating to sttp-apispec 0.7.1, I think, I found a regression regarding nullability.
Having defined:
This results in the following openapi definitions:
sttp-apispec
0.3.2
(openapi:3.0.3
):sttp-apispec
0.7.1
(openapi:3.0.3
):sttp-apispec
0.7.1
(openapi:3.1.0
):After updating, we get
type: "null"
in our openapi spec (version3.0.3
), which seems be invalid (see: https://swagger.io/docs/specification/data-models/data-types/). I think, it is only introduced in openapi version3.1.0
.