Skip to content

Don't use possible number pattern to determine number type#36

Merged
marmelroy merged 1 commit intomarmelroy:masterfrom
fikus:dont-use-possible-pattern-for-type
Mar 24, 2016
Merged

Don't use possible number pattern to determine number type#36
marmelroy merged 1 commit intomarmelroy:masterfrom
fikus:dont-use-possible-pattern-for-type

Conversation

@fikus
Copy link
Copy Markdown
Contributor

@fikus fikus commented Mar 18, 2016

The phone number type determination should never use the possible
number pattern, since that pattern is generic and not necessarily
specific to the type in question.

Update isNumberMatchingDesc to always use the national number pattern,
not the possible number pattern.

Also found and fixed a bug in RegularExpressions matchesEntirely while
making this change.

The phone number type determination should never use the possible
number pattern, since that pattern is generic and not necessarily
specific to the type in question.

Update `isNumberMatchingDesc` to always use the national number pattern,
not the possible number pattern.

Also found and fixed a bug in RegularExpressions matchesEntirely while
making this change.
@marmelroy
Copy link
Copy Markdown
Owner

Sorry for the delay with this PR. Was travelling. Looks great.

Thanks again @fikus.

@marmelroy marmelroy merged commit 42b6090 into marmelroy:master Mar 24, 2016
@fikus fikus deleted the dont-use-possible-pattern-for-type branch March 28, 2016 22:42
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