fix(subscriptions): force uppercase on payment card holder input - #74
Conversation
|
Warning Review limit reached
More reviews will be available in 35 minutes and 48 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 We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Repository UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
✨ 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 |
Why
The "add card" dialog in Profile auto-uppercases the cardholder name as you type and stores/displays the normalized value. The subscription payment dialog had no such formatter — lowercase input was accepted on screen but fails the
^[A-Z ]+$validator on submit, and the preview/payload sent raw (unnormalized) text. Two dialogs with the same field behaved differently.What
_CardHolderTextInputFormattertosubscription_payment_dialog.dart(same formatter as insave_card_dialog.dart) — forces uppercase as the user types._normalizedCardHoldergetter (trim().toUpperCase()), used for the payment payload and the card preview.How to test