Fix(isEmail): Added support for internationalized domain names #2473
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
|
Add tests too |
|
Went ahead and added tests for isEmail and isURL with the new option, allow_idn, set to false. |
|
Please update the README as well, see the checklist in the PR description |
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.
Added the
allow_idnoption which is passed down toisFQDNto check if the domain name contains non-ASCII characters. It defaults to true to maintain original behavior. If set to false, it rejects domain names in non-Latin alphabets like Arabic, Chinese, Cyrillic, etc.Closes #2390
References
For more information on IDNs, please refer to the following:
Checklist