Skip to content

Add money-plane and LATAM globe Lottie illustrations - #3579

Merged
innolope-dev merged 2 commits into
devfrom
innolope/banking-lottie-planes-globes
Oct 5, 2026
Merged

innolope-dev merged 2 commits into
devfrom
innolope/banking-lottie-planes-globes

Conversation

@innolope-dev

Copy link
Copy Markdown
Collaborator

Follow-up to #3562 and #3578. Adds 8 more Lottie illustrations to src/assets/illustrations/lottie/, in the same mascot-free style.

Money planes (the paper plane is a folded banknote)

  • bill-fold-plane: a dollar bill folds itself into a plane and flies off
  • plane-coin-drop: the plane drops coins into an open wallet
  • plane-skywriting: the plane writes a $ with its trail
  • plane-squadron: three planes in formation, for bulk payouts
  • plane-delivery: the plane dives into a phone, which gets a check

LATAM globes

  • globe-latam: globe facing the Americas with $, R$, S/, Bs and Q coins orbiting
  • globe-latam-route: pins on Mexico, Brazil and Argentina; a coin hops between them and switches currency on each landing
  • globe-world-route: the same route, then the globe turns to Europe for € and £ stops and spins back to LATAM (196-frame loop)

The folder README now lists all 52 files. Assets only; nothing imports them.

Five paper-plane loops where the plane is a folded banknote, plus three
globe loops: LATAM currencies orbiting the Americas, a Mexico-Brazil-
Argentina pin route, and the same route rotating on to Europe for EUR
and GBP stops.
@vercel

vercel Bot commented Oct 5, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
peanut-wallet Ready Ready Preview Oct 5, 2026 11:31pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration
  • Configuration used: Repository: peanutprotocol/peanut-ui/.coderabbit.yaml
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 94d2efc6-8ff5-4976-8a9b-fa07c3e2001a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
  • Autopilot · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

Code-analysis diff

Painscore total: 9157.22 → 9157.22 (0)
Findings: 0 net (+0 new, -0 resolved)

@innolope-dev
innolope-dev enabled auto-merge October 5, 2026 22:07
@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

🧪 UI test report — ✅ all green

Suites

  • ✅ unit: 10962 ran, 0 failed, 0 skipped, 2.6m

📊 Coverage (unit)

metric %
statements 83.3%
branches 73.6%
functions 78.2%
lines 84.5%
⏱ 10 slowest test cases
time test
🐢 9.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › Network failure keeps loading while retries remain, then shows the generic error
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_MERCHANT_RECENT_REFUND fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_SOURCE_OVER_MONTHLY_CAP fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › User KYC not approved fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › routes the KYC rejection on its wire code, and does not retry it
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_USER_NOT_PROVISIONED fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › MANTECA_MERCHANT_VOLUME_NEAR_CAP fails fast with copy that names the real cause
4.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › a refused idempotency key tells the user to scan again, not to contact support
3.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › Scan that recovers on the retry lands on the payment screen, not an error
3.0s src/app/(mobile-ui)/qr-pay/__tests__/qr-pay-states.test.tsx › Going offline blames the connection, and reconnecting clears it for the recovered scan
📍 Inline annotations are in the **Unit test report** check above. Coverage artifact: `coverage-unit`. Generated by `.github/workflows/tests.yml`.

@chip-peanut-bot chip-peanut-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Chip review — no blocking findings — this is not an approval

One minor animation keyframe ordering defect; no blocking findings.

Findings

  • MINOR · src/assets/illustrations/lottie/globe-world-route.json:1 · Keep the final Europe coin scale keyframes in time order
    The third Europe coin has scale keys at frames 154, 160, 156, then 162 while it remains visible through frame 162. The backward 160→156 step makes the renderer interpolate or jump through the wrong segment as the coin exits, causing a visible scale glitch. Remove or reorder the 156 key and keep the intended 160→162 exit in ascending frame order.

Checked clean

  • Pinned head and merge base matched the supplied SHAs; PR author and target matched.
  • All eight new JSON files parsed, use the declared 1050×1000/30-fps format, and contain no external image or font assets.
  • All new layer parent references resolved; recursive keyframe-order scan found no other descending tracks.
  • CI checks were still running when inspected; no completed check had failed.

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: c0a605bcafa4 · Context: repo · Took 5m

@github-actions

github-actions Bot commented Oct 5, 2026 •

Copy link
Copy Markdown
Contributor

English · Español · Español (Argentina) · Português (Brasil)

Open screen library dashboard

After merge: b89db49 → 91c954b. Capture complete in all locales.

@github-actions

github-actions Bot commented Oct 5, 2026

Copy link
Copy Markdown
Contributor

🖼 Visual diff — 5 screens moved

8 of 258 shots changed · 250 identical · baseline b3661e4 → head c0a605b

worst % screen widths
69.92% early-user 320, 430
42.05% avatar-picker 320, 430
1.39% guest-invite 320, 430
0.34% home-card-info-failed 320
0.28% withdraw-bank-form-us-resident 430

job summary · before/after/diff images — artifact

Fixture screenshots, no backend. Advisory — this check never blocks a merge. Posted from the default branch by ds-shots-comment.yml; the report it renders is untrusted data.

@innolope-dev
innolope-dev merged commit 91c954b into dev Oct 5, 2026
37 checks passed

This branch was successfully deployed

1 active deployment
Preview — ea98dbd8 Deployed Oct 5, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant