Change email regex match to fullmatch #446
Merged
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
This PR is about the current method used to conditionally match user and domain regex to email. currently, it's using match which wrongfully accepts entries if domain has special characters after .com it currently accepts, john@voluptuous.com> or john!@voluptuous.org!@($*! thus, we need to fullmatch the domain or user to avoid such entries and validate them properly.
|
Thanks! |
# for free
to join this conversation on GitHub.
Already have an account?
# 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 about the current method used to conditionally match user and domain regex to email.
currently, it's using match which unwarrantedly accepts entries if domain has special characters after .com
it currently accepts, john@voluptuous.com> or john!@voluptuous.org!@($*!
thus, we need to fullmatch the domain or user to avoid such entries and validate them properly.