[messages] require phone numbers uniqness - #266
Open
capcom6 wants to merge 2 commits into
Open
Conversation
🤖 Pull request artifacts
|
capcom6
force-pushed
the
messages/validate-phone-numbers-uniqness
branch
from
August 18, 2026 01:21
58f450d to
69fa616
Compare
capcom6
force-pushed
the
messages/validate-phone-numbers-uniqness
branch
from
August 20, 2026 00:53
69fa616 to
67c706b
Compare
capcom6
force-pushed
the
messages/validate-phone-numbers-uniqness
branch
from
August 21, 2026 03:54
d0190ee to
65f863f
Compare
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
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.
Greptile Summary
The PR enforces recipient phone-number uniqueness after normal validation and improves client-facing duplicate-ID and validation errors.
Confidence Score: 5/5
The PR appears safe to merge because no blocking failure remains.
No blocking failure remains.
Important Files Changed
Flowchart
%%{init: {'theme': 'neutral'}}%% flowchart TD A[Message request] --> B[Validate and normalize phone numbers] B --> C{Normalized number already seen?} C -- Yes --> D[Return validation error] C -- No --> E[Record number] E --> F{More recipients?} F -- Yes --> B F -- No --> G[Prepare and enqueue message]Reviews (5): Last reviewed commit: "[lint] ignore FCM Fid migration" | Re-trigger Greptile