-
Notifications
You must be signed in to change notification settings - Fork 110
Lk phone numbers update get #1179
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
Conversation
🦋 Changeset detectedLatest commit: 8dd9d4a The changes in this PR will be included in the next version bump. Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR 💥 An error occurred when fetching the changed packages and changesets in this PR |
| // PurchasePhoneNumberRequest - Request to purchase phone numbers | ||
| message PurchasePhoneNumberRequest { | ||
| repeated string phone_numbers = 1; // Phone numbers to purchase (e.g., ["+1234567890", "+1234567891"]) | ||
| string sip_dispatch_rule_id = 2; // Optional: SIP dispatch rule ID to apply to all purchased numbers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This might be misleading, since it's not linking that rule ID to the number, it's cloning the rule, right?
So to update a rule for all numbers, one would update the rule and then update numbers with that rule ID again.
Worth documenting it or adding rule id to the number model directly, if we want to link them persistently.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It isn't meant to be a clone. I've made it consistent by using sip_dispatch_rule_id in PurchasedPhoneNumber
Adding update and get apis for purchased phone numbers