Support OAS 3.1 #3577
Replies: 5 comments 10 replies
-
Good call-out @black-snow still waiting for the third-party libraries to catch up 👀 |
Beta Was this translation helpful? Give feedback.
-
not stale Haven't check for a while, has anything happened here in the meantime @nijikokun ? https://spec.openapis.org/oas/v3.1.0 is out. |
Beta Was this translation helpful? Give feedback.
-
Could you give a specific example, please, of something you need from OAS 3.1? It will help get the ball rolling. |
Beta Was this translation helpful? Give feedback.
-
This is a real issue. I don't remember all of what's added in 3.1, but it's very important to be able to put descriptions alongside the use of references. I can't imagine why this was ever prohibited. For example, if you've defined a schema called Rectangle and you want to use it by reference in various places in your API, pre-3.1 OpenAPI wouldn't let you describe what you were using it for in each instance. Baffling. |
Beta Was this translation helpful? Give feedback.
-
for what it's worth: our upstream already merged support for OSA 3.1 APIDevTools/swagger-parser#191 but they're having trouble making an npm release: APIDevTools/swagger-parser#191 |
Beta Was this translation helpful? Give feedback.
-
Is your feature request related to a problem? Please describe.
OAS 3.1 hasn't settled yet but is quite close to being final (afaik). I couldn't find any issue / roadmap tracking progress for this - please close the issue & hint me if I'm blind.
Describe the solution you'd like
Support OAS 3.1 RC0 / JSON-Schema 2019-09 and keep on improving until it's final.
Beta Was this translation helpful? Give feedback.
All reactions