Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Swagger UI 3.0 #603

Open
zhangalex opened this issue Apr 14, 2017 · 9 comments
Open

Swagger UI 3.0 #603

zhangalex opened this issue Apr 14, 2017 · 9 comments

Comments

@zhangalex
Copy link

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
Copy link
Member

dblock commented Apr 21, 2017

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

@LeFnord
Copy link
Member

LeFnord commented Apr 21, 2017

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
Copy link

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
Copy link
Member

LeFnord commented Apr 1, 2019

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

@run27017
Copy link

Does not update any more?

@synth
Copy link

synth commented Aug 26, 2021

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
Copy link

mscrivo commented Aug 14, 2023

@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
Copy link

@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
Copy link
Member

LeFnord commented Aug 15, 2023

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

7 participants