Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR updates the en-KE (Kenya) regex in the phones object to properly validate Kenyan mobile numbers against the Communications Authority of Kenya (CA) Telecommunication Numbering Plan.
It only checks that the number begins with 7 or 1 after the country code, then blindly accepts any 8 digits. This means invalid prefixes such as 071, 074, 076, 079, 010, 0118, 019, etc.which are not assigned to any Kenyan mobile operator , incorrectly pass validation.
From:https://www.ca.go.ke/sites/default/files/CA/Numbering%20Plan/Telecommunication%20Numbering%20Plan%20for%20Kenya%20May%202025.pdf it now validates the "valid ranges" eg. isMobilePhone('0710000000', 'en-KE') //false