🎉 Support passing spec a JSON object #5
Merged
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
Enhances the OpenAPIBlock to be able to accept a spec object as well as a spec url.
Related Issue
n/a
Motivation and Context
Flexibility mostly. Having the spec in the project will enable it to be enhanced with things like code samples and will enable easier searching.
How Has This Been Tested?
I whipped through the specs at: https://github.com/OAI/OpenAPI-Specification/tree/master/examples
Passing them in as
specUrl
andspec
.Screenshots (if appropriate):
n/a the page looks the same regardless of the input.
Types of changes
Checklist: