fix(TASK-22713): restore playful QR payment messages - #3233
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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 |
Code-analysis diffPainscore total: 8046.23 → 8051.06 (+4.83) 🆕 New findings (7)
✅ Resolved (5)
📈 Painscore deltas (top movers)
|
🧪 UI test report — ✅ all greenSuites
📊 Coverage (unit)
⏱ 10 slowest test cases
|
|
/chip review |
There was a problem hiding this comment.
Chip review — no blocking findings — this is not an approval
No findings.
Checked clean
- Confirmed the detached worktree head and merge base match the supplied SHAs, then reviewed all three changed files and their relevant history.
- Verified the Paying view still follows the existing QR payment state transition and only replaces its presentation component.
- Checked the translated loading-word catalogs and es-AR fallback, random non-repeating selection, 1.8-second cadence, and interval cleanup.
- Exact-head format, typecheck, lint, unit, native-export, and aggregate CI checks passed. The non-gating ds-shots job exited during its build step before screenshots with no code-specific diagnostic; locale capture jobs were still running when reviewed.
- The detached worktree has no installed dependencies, so a local targeted Jest rerun was unavailable; the exact-head unit CI suite passed.
Security review: did not run — this change has no security, privacy or money surface, so it was not asked. This review is one reviewer short.
Third opinion by claude-opus: 0 finding(s), marked with the model name. It answers only product truth, missing tests and the cross-repo contract, so treat its findings as advice.
Exact head: 2c7827777a6d · Context: repo · Took 7m
|
/chip review |
Chip review — no blocking findings — this is not an approvalNo findings in the QR payment processing-message restoration. Checked clean
Security review: did not run — this change has no security, privacy or money surface, so it was not asked. This review is one reviewer short. Third opinion by Exact head: |
QR payments lost their rotating messages when #3225 adopted the shared processing screen. Restore the existing translated message pool at the original 1.8-second cadence in the QR Paying view, while keeping the shared mascot and layout.
Adds the real QR processing view to
/dev/loading-wordsfor visual checks. Payment execution, the Paying transition, rewards and other payment flows are unchanged. No backend dependency or release flag.Task: TASK-22713
Validation: full formatting check, TypeScript, changed-file ESLint, and all 629 unit suites passed (7,780 tests; 7 skipped). Actual component checked at a 375×667 viewport in English, Latin American Spanish, Argentine Spanish and Brazilian Portuguese: messages rotate, translations render, reduced motion stops the mascot, and there are no browser page errors. This is a presentation preview, not a payment end-to-end test.
Production build passed after syncing with the latest dev mascot update. Existing upstream build warnings remain.
Screenshots
Actual QR processing component at a mobile viewport. Images are from the presentation preview.
Screenshots use immutable commit links. The temporary screenshot branch is no longer present.