Open API Schema - for Redocly #820
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
API documentation migrating to Redocly instead of local Swagger UI
What user problem are we solving?
Swagger UI too confusing to setup and the UI looks a bit ugly. Fortunately, there is a better solution called Redocly.
What solution does this PR provide?
Provide the
/openapidirectory containing our api documentation for Redocly to ingest and display beautifullyTesting Methodology
*.yamlfiles underopenapi/directory using VSCodeopenapi/Any other considerations
make sure redocly works for our case and we aren't incurring extra cost