More functional regex for URL parsing #8
Closed
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
Based on stephenhay work as seen on https://mathiasbynens.be/demo/url-regex
|
The parens issue is exactly why we're using a simpler regex: aca71b8 |
|
Oh, good to know! |
|
I think this would be a better solution: kevva/url-regex#35 (comment) |
|
Great! Then closing in favor of #9 😺 |
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.
This PR is more for a discussion about URL parsing than a direct PR.
Just found that a lot of URLs has been excluded with the actual regex, then I tried to find something better.
My proposal is based on Stephen Hay work as seen on https://mathiasbynens.be/demo/url-regex.
Still excluding parentheses, so links like
https://en.wikipedia.org/wiki/Kansas_(disambiguation)are not well parsed.🚀