Feature Request: OpenAPI Spec 3.1

[xiaoxiangmoe]

OAS 3.1 was released, can we support OpenAPI Spec 3.1?
OSA 3,1 has some new feature, such as namedEnum and so on.

[rk3rn3r]

+1 Would be great to have patternProperties from that JSON Schema draft 2020-12 extension which is part of OAS3.1.

[DepickereSven]

Then could this issue be fixed to #3900

[daltontc]

+1 The ability to do explode for multipart/form-data arrays would be a great feature.

[frantuma]

we have 3.1 in our short term roadmap, please check this comment in swagger-parser for details

[frantuma]

#4129 introduces support for OAS 3.1 representation (swagger-models), serialization and deserialization. code first resolution of OAS 3.1 spec in ModelResolver and JAXRS Reader (both via conversion and additional annotations resolution) is on the way

[Xbloud]

The OpenAPI 3.1 is out for more than a year. The referenced short term roadmap is 0.5 year old and the current version still does not support OpenAPI 3.1 features. I am especially interested in a feature allowing addition any sibling properties next to $ref in object schema (generating OpenAPI spec from java annotations). Can you, please, provide refined roadmap?

[Fares-Harri]

is there any update about supporting OpenAPI 3.1?

[frantuma]

Swagger Core does support OAS 3.1 in terms of representation, (de)serializaization and resolving. Please see wiki for details