Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add FAQ for vanity numbers / parsing with non-digit characters #1834

Merged
merged 6 commits into from
Jul 5, 2017
Merged

Add FAQ for vanity numbers / parsing with non-digit characters #1834

merged 6 commits into from
Jul 5, 2017

Conversation

keghani
Copy link
Contributor

@keghani keghani commented Jul 4, 2017

cl/160892622
b/30128207

Please don't merge unless release is done.


This change is Reviewable

@keghani keghani requested a review from lararennie July 4, 2017 14:29
FAQ.md Outdated
If the input looks like a vanity number to the library, `parse()` assumes this
is intentional and converts alpha characters to digits. Please read the
documentation for
[`parse()`](http://github.com/googlei18n/libphonenumber/blob/35210c7288b3953360289b24796330bc848dfe2d/java/libphonenumber/src/com/google/i18n/phonenumbers/PhoneNumberUtil.java#L3040)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we refer to master
(https://github.com/googlei18n/libphonenumber/blob/master/java/libphonenumber/src/com/google/i18n/phonenumbers/PhoneNumberUtil.java)

then it'll always be up to date; on the other hand the line number will change...

I think probably best to have the "master" not the specific version, and tell people to search for parse?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Done

@keghani keghani merged commit 6479eb9 into google:master Jul 5, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants