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
Which seems mighty unfortunate considering how many people probably intuitively want to use @urns.tel as the argument to things that expect a telephone number.
Detecting we are given a tel URN seems like it would probably be worth it? What are possible downsides there?
Also feels super weird that the current behavior ends up with + prefixed on the returned number.
@rowanseymour feels liken number parsing this has been under a lot of flux lately, any opinions here?
The text was updated successfully, but these errors were encountered:
urns.NewTelURNForCountry("tel:+12065551212", "US")
->tel:+tel12065551212
Which seems mighty unfortunate considering how many people probably intuitively want to use
@urns.tel
as the argument to things that expect a telephone number.Detecting we are given a tel URN seems like it would probably be worth it? What are possible downsides there?
Also feels super weird that the current behavior ends up with
+
prefixed on the returned number.@rowanseymour feels liken number parsing this has been under a lot of flux lately, any opinions here?
The text was updated successfully, but these errors were encountered: