Adding forward slash to list of prohibited domain characters #142
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
|
Thanks for both of your PRs! I will cut a release right away |
|
Thank you @micke! |
|
@pdoulatshahi i just pushed 3.1.3 to rubygems! |
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.
Currently, the code allows for a forward slash in the email address domain, but this should be a prohibited character. This pull request addresses that.
How to test
If you set the changed
PROHIBITED_DOMAIN_CHARACTERS_REGEXconstant inValidEmail2::Addressback to its current value:PROHIBITED_DOMAIN_CHARACTERS_REGEX = /[+!_\s]/you will see that the new test I have added fails.