Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Visualize the OpenAPI document at a standard URI
See original GitHub issueAt our weekly hangout today we discussed the possibility of a spec-defined URL where a user could visualize the generated OpenAPI document. The idea is that the spec would indicate how to enable/disable such a feature and specify where a user could find such a visualization. This would probably be similar to validation in approach (config property to enable/disable and well defined endpoint to load the UI) but is also open for discussion of course.
As an example of what this might look like for a vendor - Open Liberty provides an endpoint (e.g. /openapi/ui that results in Swagger UI being opened with the generated OpenAPI document.
Issue Analytics
- State:
- Created 5 years ago
- Reactions:2
- Comments:9 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I agree @EricWittmann
Seeing that there have been no objections to our latest proposal I added the
help wantedlabel so anybody can pick this up and complete it.Well, I would say that implementors are always free to offer whatever non-conforming options they choose. So out of scope of the spec document IMO.