-
Notifications
You must be signed in to change notification settings - Fork 63
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
Valid numeric domains are considered invalid in strict mode #72
Comments
delphaber
changed the title
Valid numeric domains are considered invalid strict mode
Valid numeric domains are considered invalid in strict mode
Apr 1, 2021
karlwilbur
added a commit
that referenced
this issue
Apr 5, 2021
* bugfix-72-fix-regexp-for-numeric-domains: Fix regexp for numeric domains (fixes #72) Add `EmailValidator::Error` class, raise `EmailValidator::Error` when invalid `mode` Add checks for double dash in domain Fix specs for numeric-only domains labels Add checks for numeric-only TLDs in tests Add tests to ensure that `regexp` returns expected value Add failing test: strict mode should accept numbers only domains
karlwilbur
added a commit
that referenced
this issue
Apr 5, 2021
* develop: Bump version to `2.2.3` Fix regexp for numeric domains (fixes #72) Add `EmailValidator::Error` class, raise `EmailValidator::Error` when invalid `mode` Add checks for double dash in domain Fix specs for numeric-only domains labels Add checks for numeric-only TLDs in tests Add tests to ensure that `regexp` returns expected value Bump y18n from 3.2.1 to 3.2.2 Add failing test: strict mode should accept numbers only domains Update .travis.yml
Thank you! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Emails from domains like 163.com, 139.com are marked as invalid. But they are valid: those are common emails in China :)
I've created a failing PR for this
The text was updated successfully, but these errors were encountered: