fix: adds support for URL-encoded whitespaces#37
Merged
IonicaBizau merged 1 commit intoIonicaBizau:masterfrom Nov 14, 2024
Merged
Conversation
c52d5b7 to
070e23b
Compare
Updates parse-url dependency from v8 to v9.
070e23b to
576d8a1
Compare
Merged
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
2 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.
v8 of
parse-urldoesn't support URL-encoded whitespaces (i.e.:%20). These are needed for Azure DevOps repositories with spaces in their name (and, likely, others).Updating to v9 of
parse-urlresolves the issue.This also includes a small fix to the test file to remove some duplicated properties in an object.
Fixes #36