Fix URL parsing to include delimiters before slashes#100
Merged
robinst merged 2 commits intorobinst:mainfrom Apr 12, 2026
Merged
Fix URL parsing to include delimiters before slashes#100robinst merged 2 commits intorobinst:mainfrom
robinst merged 2 commits intorobinst:mainfrom
Conversation
Add tests for URLs with delimiters followed by slashes, addressing issue robinst#90.
Owner
|
Awesome, thank you! |
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.
A slash can be the end of a URL if the previous character is a valid URL character. This means that delimiters like
!or.before a/are included in the URL, e.g./!/, but non-URL characters (like non-ASCII when IRI parsing is disabled) before a/are not.Fixes #90