Validation: 11 digit Indian number validates to true
See original GitHub issueIt looks like the validation for Indian numbers continues to validate numbers with between 11-14 numbers. The following screen shot is with a valid Indian number:
The following is with an 11 digit (invalid) Indian phone number, which still has isValid: true
Then the following is the same situation for US numbers. First screenshot is a valid number with 10 digits with isValid: true
and the second is an invalid number with 11 digits and isValid: false
Issue Analytics
- State:
- Created 6 years ago
- Comments:10 (6 by maintainers)
Top Results From Across the Web
How to validate Indian Passport number using Regular ...
Output: true. Explanation: The given string satisfies all the above mentioned conditions. Therefore it is a valid passport number of India.
Read more >Regular Expression Validation For Indian Phone Number ...
Regular Expression to validate 11 or 12 (starting with 0 or 91) digit number ... All mobile numbers in India start with 9,...
Read more >JavaScript: HTML Form - Phone Number validation
At first, we validate a phone number of 10 digits with no comma, no spaces, no punctuation and there will be no +...
Read more >Simple Way to Validate Phone Numbers in PHP
An easy walkthrough of how to validate phone numbers in PHP. ... Let's say that the genuine phone number is 10 digits long,...
Read more >[Solved] How to check only 10 digit mobile number regex
So ... the data you are checking is not what you think it is. Use the debugger to check exactly what is in...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Oh, man, I mislead you a bit on this one. Actually, use ‘isValidNumberCustom’ with the full metadata as described in ‘libphonenumber-js’ readme.
On Wed, 6 Sep 2017 at 21:44, Graham Lutz notifications@github.com wrote:
So I’ve got that in place, and it’s pulling it in but does’t change anything. This is what the props on our phone component looks like:
And this is what I am using to validate:
Any other thoughts?