[Question]: Support OAS 3.2

[juan-catalan]

Question

Do you have a roadmap to add support to OAS 3.2?

There a few features that are really valuable for our team, like the Multipurpose tags with nesting.
I have found an official page where it describes swagger support for openapi-3-2-0 but it does not show information about swagger-core.

Thanks for your work and time

[Mattias-Sehlstedt]

Hi @juan-catalan,

I can begin by clarifying that I am only a contributor to the OAS-ecosystem. I.e., I am not connected to Swagger/SmartBear in any way.

---

I believe the blog post is first and foremost referring to swagger-api/swagger-ui#10721, where swagger-ui got the capability to visualize OAS 3.2 concepts in the UI.

For swagger-core I believe the functionality could vary depending on whether it is merely meta-data (e.g., just adding a new field to the @Schema or any other annotation, which is then just forwarded to the generated specification) or if it can be derived from code-structure (e.g., if an interface would correspond better to some OAS 3.2 concept).

If you could provide some concrete example for exactly what concept that you are interested in and how it is expected to behave I believe it could be possible for me to start investigating a draft for how to introduce it (so for example sharing the definition that you find best captures Multipurpose tags with nesting). This so it is possible to build and implementation together with tests that showcase that the behavior is as expected.

Most OAS 3.1 concepts were introduced as annotation fields as this.

[Mattias-Sehlstedt]

I found that the OAS 3.2 documentation was simple enough for the new tag fields, so I have began with a branch where I investigate how to best incorporate these fields into the specification generation.

I found examples too at https://learn.openapis.org/examples/.

[juan-catalan]

Hi @Mattias-Sehlstedt,

Thanks for you work and effort, I will keep an eye on your progress.