feat: addition of an init and methods for pulling spec extensions
#537
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
erunion
added
enhancement
erunion
changed the title
init and getExtension() methodsinit and methods for pulling spec extensions
2 tasks
domharrington
approved these changes
Nov 5, 2021
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.
🧰 Changes
Oas.init()method that will do type transformation on raw JSON objects before it's sent into theOasconstructor. This helps so that we don't need to exportRMOAS.OASDocumentand you can donew Oas(petstore)out of the box.hasExtension()andgetExtension()methods to bothOasandOperationfor spec extensions lookups. We can use this in @readme/oas-extensions to clean up some work there.🧬 QA & Testing
See tests.