Repository navigation
fix(uri): avoid parsing as scheme - #953
Merged
Merged
Conversation
kevinschweikert
force-pushed
the
fix/uri-scheme-parsing
branch
from
October 24, 2026 16:23
b5916a4 to
dc0fea0
Compare
lpil
force-pushed
the
fix/uri-scheme-parsing
branch
from
November 4, 2026 12:23
dc0fea0 to
cc8457a
Compare
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
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.
https://www.rfc-editor.org/info/rfc3986/#section-3.1
fixes
/,?, or#as implicitly closing a scheme even without a trailing colon on the JS target