Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix: #582 Incorrect text to link parsing #662

Merged
merged 2 commits into from
Sep 24, 2024

Conversation

steven-fox
Copy link
Collaborator

Closes #582

This PR updates the LinkProviderParsable to only linkify text that is a http(s) or email string.

Important: Before this PR, text like example.com would be converted to a link. After this PR, this will no longer happen. example.com and blade.php currently match the regex pattern, so I fixed #582 by simply looking for the string to start with http(s) or to be an email match.

If we want to retain that example.com should linkify functionality, we will have to change the parsing logic to identify valid top-level domains, I guess? That's like 400+ possible values so I didn't go that route for this quick change.

I'll leave it up to you guys to decide what's most important.

@steven-fox steven-fox linked an issue Sep 24, 2024 that may be closed by this pull request
@steven-fox
Copy link
Collaborator Author

steven-fox commented Sep 24, 2024

LOL

This is a funny incorrect parsing from production just now.

image

... (later) and another one I just saw
image

@nunomaduro nunomaduro merged commit 48eebf7 into main Sep 24, 2024
@nunomaduro nunomaduro deleted the 582-incorrect-text-to-link-parsing-for-bladephp branch September 24, 2024 09:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Incorrect text-to-link parsing for ".blade.php"
2 participants