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
Starting in 5.3.1, a US phone number of correct length (example: '+1 111 111 1111') returns "invalid" possibility. In 5.3.0, it correctly returns "is-possible". This is contrary to the readme, which states "quickly guesses whether a number is a possible phone number by using only the length information, much faster than a full validation". Also, in libphonenumber's source, the function only checks length for a given reason.
This affects all versions of awesome-phonenumber after 5.3.0.
minorbug
changed the title
Since 5.3.1, possibility incorrect for US "+11111111"
Since 5.3.1, possibility incorrect for US "+1 111 111 1111"
Jun 27, 2023
Starting in 5.3.1, a US phone number of correct length (example: '+1 111 111 1111') returns "invalid" possibility. In 5.3.0, it correctly returns "is-possible". This is contrary to the readme, which states "quickly guesses whether a number is a possible phone number by using only the length information, much faster than a full validation". Also, in libphonenumber's source, the function only checks length for a given reason.
This affects all versions of awesome-phonenumber after 5.3.0.
5.3.0: https://js-cc6s3q.stackblitz.io
5.3.1: https://js-b8urus.stackblitz.io
libphonenumber demo page: https://htmlpreview.github.io/?https://github.com/google/libphonenumber/blob/master/javascript/i18n/phonenumbers/demo-compiled.html
The text was updated successfully, but these errors were encountered: