Openapi 3.1 support in the model

[hamnis]

https://github.com/OAI/OpenAPI-Specification/releases/tag/3.1.0

[adamw]

Related: https://github.com/swagger-api/swagger-ui/issues/5891

[rojekp]

So far, I added new fields for 3.1.0 OpenAPI model.

[adamw]

We have to wait until Swagger supports 3.1

[yoohaemin]

Is it a possibility that tapir maintains support for both 3.0.x and 3.1 for some time? I understand Swagger is the immediate blocker, but even after that there might be other tooling that may still be stuck on 3.0.x 🤔

I'm a bit careful with this request though, because it will be a burden for the maintainers of this repository.

[adamw]

@yoohaemin I think we'll rather switch to 3.1 at some point. Maintaining two branches might be problematic. But not impossible - would be a matter of creating two separate documentation interpreters.

[adamw]

But please vote on the issue (with 👍 ) so that we can see how popular it is :)

[LeifW]

We've switched from swagger-ui to stoplight elements, as it gives a much nicer view of our API, and stoplight elements supports openapi 3.1

[adamw]

This is already done in the model, will be supported once swagger 5.0 is done in #2958