-
Notifications
You must be signed in to change notification settings - Fork 52
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
520.347.9933 x3179 is not a phone number #20
Comments
Why are you not opening this as an issue with google? Because I agree with this assessment on phone numbers |
Can't believe that this issue is still not fixed in the current version... |
What do you want it to do? Please be clear because conforming to some google library parser may not be correct. What I mean by clarity is write a test optimally or describe the Like: |
@Siliconrob |
How are you supposed to handle extensions? Because phone numbers do have extensions. Even this google parser thing says that.
Maybe what you want is an override to not return phone numbers with extensions, but that would be limiting your dataset responses and give the false confidence in your workflows because someone will come along with a phone number that does have an extension and what do you do then? |
I'm not sure if we understand each other. |
You wouldn't dial the If it was a human you would dial first part, connect, wait for automated routing system to respond and then dial extension number etc. I mean it is a bit more rare to have an input enter a phone number with an extension because sharing a phone line is mostly a business operation and nowadays emails are probably better than messing with the hassle of internal extensions. |
version: 1.5.148
The generated phone numbers are not valid?
The text was updated successfully, but these errors were encountered: