[Enhancement] Integrate ReDoc OpenAPIParser #148
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
|
Size Change: 0 B Total Size: 3.38 MB ℹ️ View Unchanged
|
|
Visit the preview URL for this PR (updated for commit 33503a7): https://docusaurus-openapi-36b86--pr148-dyh9wj3p.web.app (expires Fri, 05 Aug 2022 21:56:04 GMT) 🔥 via Firebase Hosting GitHub Action 🌎 |
sserrata
changed the title
|
Now that we have a working solution for handling circular |
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.
Description
This PR introduces the redoc OpenAPIParser class, which could be useful for merging and resolving schemas, refs and other OpenAPI datatypes.
Motivation and Context
It's possible that these utilities could be used to handle edge cases, i.e. the parts of the spec that remain unresolved following the initial parsing.
How Has This Been Tested?
I performed various tests offline to determine its effectiveness. In short, it works, but we'll need to understand how to best leverage it to accomplish our goals.
Next steps
Test against spec files we know to contain unresolved
$refpointers.