feat: joinRelativeURL
#220
Merged
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
danielroe
reviewed
Mar 13, 2024
danielroe
reviewed
Mar 13, 2024
danielroe
reviewed
Mar 13, 2024
danielroe
approved these changes
Mar 15, 2024
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.
Context: #37 > #217 > #218
This PR reverts back
joinURLbehavior to 1.4.0 (latest release) and adds support of joining URLs with relative../paths with newjoinRelativeURLutility.The reason for this decision is to avoid potential behavior changes as the current
joinURLbehavior is depended in many places. (alsoresolveURLandnormalizeneed to follow a consistent change)In next major release we might join behavior (but if anything diverging from
joinRelativeURL, we keep it's behavior as is forjoinRelativeURLto not break another segment of usages)