Fix issue where the replacement of double-slash was over-aggressive #151
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.
Pre-flight Checklist
Description of Change
The previous fix for handling trailing
/
in the urls was overly aggressive in removing double-/
- due to which if an embedded url in the query string was present, that would also go fromhttp://<>
tohttp:/<>
. This PR fixes that and also adds a unit test for the same to avoid regression.Fixes #141
Motivation and Context
Screenshots
Checklist
npm run prepare-code
)npm test
passesRelease Notes