Top OpenAPI-Specification issues

Integer enum with named items

Post 3.0 Proposal
kenjitayama picture kenjitayama·5 May 2016·34 Comments
👍53 ❤5

Support for multiple request/response models based on headers

OpenAPI.Next Proposal Sub Issue
jahlborn picture jahlborn·9 Oct 2014·99 Comments
👍37

Proposal: Default responses for all endpoints

OpenAPI.Next Proposal Sub Issue
sebastian-demel picture sebastian-demel·5 Dec 2015·20 Comments
👍97

add "null value support" in spec?

OpenAPI.Next Proposal
fehguy picture fehguy·21 Dec 2014·117 Comments
👍35

Allow requestBody for the DELETE method.

adjenks picture adjenks·8 Jan 2019·21 Comments
👍45 ❤12

“Websocket” communication specification. Alternative (non-REST) way to communicate

OpenAPI.Next Proposal Sub Issue
artem-korolev picture artem-korolev·11 Dec 2015·39 Comments
👍31

Swagger for WebSocket services

OpenAPI.Next Proposal Sub Issue
sten picture sten·14 May 2014·22 Comments
👍63

Support an operation to have multiple specifications per path (e.g. multiple POST operation per path)

OpenAPI.Next Proposal Sub Issue
DavidBiesack picture DavidBiesack·28 Oct 2014·55 Comments
👍65 👀1

Support for multiple $refs inside a single object

$ref
glen-84 picture glen-84·17 Jul 2015·34 Comments
👍79

Proposal: x-oas-draft-alternativeSchemas

draft-feature pilot
darrelmiller picture darrelmiller·9 Apr 2018·117 Comments
🎉20 👍13
 Previous issues
Next issues