added failing German mobile number to tests #18
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Formatting this mobile number will fail right now as the leading zero is missing in the national format.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Formatting this mobile number will fail right now as the leading zero is missing in the national format.
This is just an example that should proof the issue #12 can not be fixed by the proposal there in case it is a certain mobile carrier prefix and not a fixed landline.
The error in formatting comes from the underlying library (https://libphonenumber.appspot.com/phonenumberparser?number=%2B491520123123&country=DE&geocodingLocale=de-DE). I filed an issue there but as soon as it get fixed there, adding a test here makes sense to me.
https://issuetracker.google.com/issues/247105388