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
{{ message }}
This repository has been archived by the owner on Jul 1, 2020. It is now read-only.
Can you please tell me how I can validate a European phone number ?
(in other words... can you please add a regular expression for this, like you did for euro_date ?)
Some test data (for Belgium)
+32 ppp xx xx xx (mobile number in Belgium, always 3 digits for the provider)
+32 a xxx xx xx ( land number with one digit for the area)
+32 aa xx xx xx ( land number, with 2 digits for the area)
I will push a new revision soon for a small fix, then I started looking at the Regex you provided. This seems like a Regex for internal phone number, not really specific to Europe and it seems very loose since it's only checking for last numbers to be between 6 and 14.
I could maybe add this as phone_international, but is it really what you want, is it strong enough?
Since I add to push a new revision for another fix, I added as well the Regular Expression pattern that is mentioned in your article to create the new phone_international validation. It is now part of the latest version 1.5.4, be sure to update the package.
On another note, you wanted to know how to add a regex. You can use Regex directly with Angular-Validation see this Wiki - Regular Expression Pattern
Hi sir,
Can you please tell me how I can validate a European phone number ?
(in other words... can you please add a regular expression for this, like you did for euro_date ?)
Some test data (for Belgium)
+32 ppp xx xx xx (mobile number in Belgium, always 3 digits for the provider)
+32 a xxx xx xx ( land number with one digit for the area)
+32 aa xx xx xx ( land number, with 2 digits for the area)
this algorithm covers almost all possibilities in Europe
Thanks in advance for your reply,
Kind regards,
Johnny Driesen
The text was updated successfully, but these errors were encountered: