-
-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
OpenAPI Viewer #20852
Comments
Yes, it would be nice! I am currently trying to switch to Gitea from Gitlab and this has been missing from my list |
Since iframe will be introduced in #20180, this becomes possible. |
Probably good to iframe it, yes. |
Thought, we could also do without backend support and just create the iframe in JS, like already done for mermaid: gitea/web_src/js/markup/mermaid.js Line 55 in bf325d4
|
While swagger ui would not introduce new dependencies I would rather see redoc being used for this as looks way better and readable |
I find swagger-ui more readable than redoc, but that's probably because I'm used to it. To me, swagger-ui is still kind of the gold standard for openapi specs. According to https://www.wappalyzer.com/compare/redoc-vs-swagger-ui, swagger ui is more than 12 times more popular than redoc. |
I agree for swagger ui being better when you want it to be deployed with API where you can try it etc but in this case when it's only documentation display redoc has multiple advantages over swagger-ui like better display on mobile devices, easier to read nested structure documentation, better support for openapi 3 (like oneof that swagger-ui does not even support etc) |
Feature Description
GitLab has a feature where they can render openapi/swagger documents using swagger-ui in a rendered view. We should consider adding this too as we already bundle swagger-ui, so it's a almost-zero cost addition.
The text was updated successfully, but these errors were encountered: