[BUGFIX] Make Email detection in lexer more strict #573
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
So it does not catch email like expressions in backticks
jaapio
reviewed
Sep 4, 2023
| @@ -56,7 +56,7 @@ protected function getCatchablePatterns(): array | |||
| return [ | |||
| '\\\\``', // must be a separate case, as the next pattern would split in "\`" + "`", causing it to become a intepreted text | |||
| '\\\\[\s\S]', // Escaping hell... needs escaped slash in regex, but also in php. | |||
| '\\S+@\\S+\\.\\S+', | |||
| '[a-zA-Z0-9._%+-]+@[a-zA-Z0-9.-]+\\.[a-zA-Z]{2,}', | |||
There was a problem hiding this comment.
This is good enough for now... but it feels like this should be done in a different way... as emailaddreses are not easy to catch in a regex.
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.
So it does not catch email like expressions in backticks