search

swagger-api / swagger-core

Examples and server integrations for generating the Swagger API Specification, which enables easy access to your REST API
http://swagger.io
Apache License 2.0
7.37k stars 2.17k forks source link

Feature Request: OpenAPI Spec 3.1 #3913

Open xiaoxiangmoe opened 3 years ago

xiaoxiangmoe commented 3 years ago

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 commented 3 years ago

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

DepickereSven commented 3 years ago

Then could this issue be fixed to https://github.com/swagger-api/swagger-core/issues/3900

daltontc commented 3 years ago

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

frantuma commented 2 years ago

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

frantuma commented 2 years ago

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 commented 2 years ago

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 commented 2 weeks ago

is there any update about supporting OpenAPI 3.1?