swagger-core icon indicating copy to clipboard operation
swagger-core copied to clipboard

Published 20 hours ago • verified publisher icon swagger-api

Feature Request: OpenAPI Spec 3.1

Open xiaoxiangmoe opened this issue 3 years ago • 6 comments

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.

xiaoxiangmoe avatar Mar 15 '21 04:03 xiaoxiangmoe

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

rk3rn3r avatar Mar 26 '21 13:03 rk3rn3r

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

DepickereSven avatar May 31 '21 07:05 DepickereSven

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

daltontc avatar Jul 08 '21 17:07 daltontc

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

frantuma avatar Oct 06 '21 17:10 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

frantuma avatar Feb 23 '22 11:02 frantuma

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?

Xbloud avatar Apr 27 '22 14:04 Xbloud