phoenix_swagger icon indicating copy to clipboard operation
phoenix_swagger copied to clipboard

Are there any plans to provide support for OpenAPI 3.0 specification?

Open slavo2 opened this issue 6 years ago • 5 comments

Are there any plans to provide support for OpenAPI 3.0 specification?

(i.e. allowing as an option (one of options, default option or the only option) to produce (swagger) json file, conforming to OpenAPI 3.0 specification (Current is 3.0.1 : https://github.com/OAI/OpenAPI-Specification/blob/master/versions/3.0.1.md )

slavo2 avatar Jul 05 '18 14:07 slavo2

I'm looking for callback support which I believe requires version 3. If there is something I can do to help this process I'd certainly be interested in a discussion

sevandewater avatar Sep 05 '18 14:09 sevandewater

The difficulty comes from trying to support 2.0 and 3.0 simultaneously.

One place to start would be to support validations against an existing swagger 3.0 JSON document. Check the version in the info section and use a different backend module accordingly.

mbuhot avatar Sep 06 '18 06:09 mbuhot

The difficulty comes from trying to support 2.0 and 3.0 simultaneously.

Could that be solved by the library reading swagger_info and the response from swagger_info containing version specification?

slavo2 avatar Sep 06 '18 15:09 slavo2

Are there any plans for OAS3. I can help if needed 🙂

tanweerdev avatar Mar 19 '20 13:03 tanweerdev

@tanweerdev I think a good place to start would be to load and validate requests against an existing OAS 3 file.

mbuhot avatar Mar 19 '20 21:03 mbuhot