-
### Describe the idea (required)
Please format phone number of POIs with https://github.com/google/libphonenumber when we displaying more details about a POI, or when we are editing details of a PO…
-
Mollie seems to require a phone number in the E.164 format (+31600000000). Currently, an error can occur e.g. with WooCommerce and the Klarna payment method:
> Unprocessable Entity - The 'phone' fi…
-
The user will not need to input parentheses or hyphens
-
Currently the library only supports UK, US and FR as countries for the phone() function. It would be nice if other countries can also be supported. This can also be done by specifying the first few di…
-
The issue is with Dutch phone numbers.
In the Netherlands, as far as I know, the numbers `0689124321` and `+31689124321` are the same and valid.
Unfortunately, both are not transferred correctly…
-
## Is your feature request related to a problem? Please describe.
The account team will is looking to add phone number support to the auro-input
## Describe the solution you'd like
![image](h…
-
Phone numbers in registrations and other forms use `mask="phone"`, as it would be guessable
That might actually confuse users, since it formats the phone number in a way to which italians aren't us…
-
Right now, `fr:us-phone` is strictly a US phone number. Possible enhancements:
- UK format ([+1 from customer](https://3.basecamp.com/3600924/buckets/1966555/messages/549369284))
- international p…
-
## Enhancement Proposal: Support for International Phone Numbers
**Component**: PhoneMask
### Current Behavior
The current implementation of PhoneMask formats phone numbers in the format `xxx-x…
-
**Describe the bug**
The IX sales_phone field is not E.164 checked/formatted. Most likely this is also true for the tech_phone field.
**To Reproduce**
```
curl -snG https://www.peeringdb.com/ap…