SWG-7516 utilizing safeURLResolver in swagger-parser-v3#1911
Merged
MiloszTarka merged 7 commits intomasterfrom Apr 24, 2023
Merged
SWG-7516 utilizing safeURLResolver in swagger-parser-v3#1911MiloszTarka merged 7 commits intomasterfrom
MiloszTarka merged 7 commits intomasterfrom
Conversation
frantuma
approved these changes
Apr 18, 2023
MiloszTarka
deleted the
SWG-7516-utilizing-safe-url-resolving-in-swagger-parser
branch
This was referenced May 2, 2023
This file contains hidden or 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
4 participants
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.
This PR makes swagger-parser-v3 to utilizes safeUrlResolver when resolving OpenAPI 3.1 definitions.
The reason behind this change is described deeply under the following PR:
#1910
The $refs are checked in ReferenceVisitor class, in readHTTP method.