You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
But the country_code for dialing is simply returned as '1' which is the same for US/CA making country information lookups using this data problematic. Twilio specifically gives ["+1829", "+1809", "+1849"] as the possible codes for DO.
Is this a bug or is there a better way to get the full dial code that I am not aware of? I've noticed similar problems with other countries that have the dial code start with '1', including Bahamas and Puerto Rico.
The text was updated successfully, but these errors were encountered:
@AdamJacobson this gem's data is based on google libphonenumber and it has "1" as country code since it is required for proper parsing, I will try to find a way to solve your issue.
Parsing a valid DO number does return 'DO' as the country:
But the country_code for dialing is simply returned as '1' which is the same for US/CA making country information lookups using this data problematic. Twilio specifically gives ["+1829", "+1809", "+1849"] as the possible codes for DO.
Is this a bug or is there a better way to get the full dial code that I am not aware of? I've noticed similar problems with other countries that have the dial code start with '1', including Bahamas and Puerto Rico.
The text was updated successfully, but these errors were encountered: