Swagger UI 3.0

[zhangalex]

Hi Guys,

This is really a great gem. Thank you.

Since swagger ui 3.0 already released, could you please tell me is there any plan on swagger UI v3?

THANKS AGAIN.

[dblock]

Nobody is working on this AFAIK. We look forward to you contributing!

[LeFnord]

yeap, nobody is official working on it, so please feel free to contribute

btw … you should reference the OAPI spec itself, not the swagger UI, this isn't a official implementation at the moment, see: implementations

[blakepettersson]

I have a local branch that works with OpenAPI 3. It's a bit rough around the edges, and I'd need some help to try to see what the next steps would be..

[LeFnord]

sounds good 😄 … can you open a PR, so others can have a look on it and helping

[run27017]

Does not update any more?

[synth]

Hi! Dropping a note that I found a workaround to easily get SwaggerUI3 working by converting your Swagger2 spec to OpenApi3, detailed here: #744 (comment)

[mscrivo]

@blakepettersson @LeFnord Really sad to not see this get over the line, you did so much great work on it! Is there a summary or list of what's left to do to get this done in case someone else wants to pick up the rest and run with it?

We're using grape and finding we're running into so many issues with the lack of OpenAPI v3 support, from no discriminated unions, to no param examples, to no bearer auth support in the security spec, etc. Converting from v2 to v3 only gets you so far and leaves a lot to be desired.

[blakepettersson]

@mscrivo it's been years since I've worked on anything Ruby-related, let alone this, so I longer have no idea on what is/was missing. Good luck for anyone wanting to further build upon it!

[LeFnord]

@mscrivo … actual, there is no such kind like a to do list for open steps

but there are a bit of work on it, see the OAPI-v3 branch
feel free to start there and contribute

[pieterocp]

It'd be nice to get the numbata:open-api3-rebased rebased again + made into the OAPI-v3 branch branch, put it in beta, update associated tooling to be 3 ready.

Is the long term plan to support version 2 for the rest of time?

Since version 3 has been out for 8 years at this point, and they're already talking about releasing version 4 sometime this year, will this tool end up having to support version 2, 3, 3.1 & 4 simultaneously?