fix(app): neutral placeholders in the WhatsApp connection modal#769
Conversation
The phone-number-id / WABA-id fields used a specific tenant's real values as
placeholders ("1188646904321987" / "1333560228881251"), which reads as pre-filled
data in a generic per-org card and is confusing (placeholders aren't submitted).
Replace with localized neutral examples (modal.phoneNumberIdPlaceholder /
wabaIdPlaceholder), matching the existing tokenPlaceholder pattern.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
|
Warning Review limit reached
More reviews will be available in 10 minutes and 55 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
|
App preview imageThe latest app preview image for this PR is ready.
|
1 participant
Problem
The WhatsApp connection modal used a specific tenant's real values as the placeholders for the phone-number-id and WABA-id fields (
1188646904321987/1333560228881251). In a generic per-org card that reads like pre-filled data — and since placeholders aren't submitted, it's misleading (you still have to type the value).Fix
Replace with localized neutral examples via i18n (
modal.phoneNumberIdPlaceholder/modal.wabaIdPlaceholder→ "e.g. 1234567890" / "ej. 1234567890"), matching the existingtokenPlaceholderpattern. No real identifiers in the component.whatsapp-connection-modal.tsx: both placeholders →tr(...)en.json/es.json: two new placeholder keys🤖 Generated with Claude Code
Closes #771