[REQ] Add support for OpenAPI 3.1

[bilalshaikh42]

Is your feature request related to a problem? Please describe.

Unable to use code generation with OpenAPI version 3.1 specifications

Describe the solution you'd like

Add support for OASv 3.1

Describe alternatives you've considered

Currently, I am simply changing the version number included in the spec and disabling spec validation. This works just fine, since the only incompatible change that I am dealing with is the use of "examples" as a list instead of a single value. While the spec is invalid when doing this, it is still parsed and generates code just fine.

This approach would not work for some of the other changes, however.

Additional Context

Here are the major changes from the release announcement:

Major Changes in OpenAPI Specification 3.1.0

• JSON Schema vocabularies alignment
• New top-level element for describing Webhooks that are registered and managed out of band
• Support for identifying API licenses using the standard SPDX identifier
• PathItems object is now optional to make it simpler to create reusable libraries of components. Reusable PathItems can be described in the components object. There is also support for describing APIs secured using client certificates.

[thetric]

Duplicate of #9083

This project website mistakenly states that it supports OpenAPI 3.x, although only 3.0 is supported:

Generate clients, servers, and documentation from OpenAPI 2.0/3.x documents

https://openapi-generator.tech/

[bilalshaikh42]

Thanks! Somehow missed it when searching.

…

On Mon, Nov 8, 2021, 11:27 AM Dominik Broj ***@***.***> wrote: Duplicate of #9083 <#9083> — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#10811 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHX4FICG3NTUDWA4PM5VYUDUK73AZANCNFSM5HSULUWA> .

[antonio-petricca]

Is it planned the support for 3.1?