Midnight redeem functions

[yushih]

Note

Implements Midnight airdrop redemption: scans address thaw schedules, shows statuses/details, and builds/signs redemption tx with collateral handling, while refactoring UI to shared i18n strings.

• Airdrop UI/Flow:
  • Add AirdropPage overhaul to scan wallet addresses for thaws, list destinations (AddressCard), and show schedule/details (AddressDetails).
  • Introduce Redeem dialog to fetch collateral, build redemption tx, handle reorg flow, and send via tx review modal.
  • Refactor dialogs/components (AbortDialog, ClaimDialog, LedgerClaimDialog, ClaimInfo, Terms, Zero) to use shared strings via useStrings.
• API/Logic:
  • Extend api/ada/midnight.js with thaw scanning (scanAddressesForThaws), thaw schedule fetch, collateral selection (getCollateralUtxos with reorg path), reorg tx creation, and redemption tx builder (getRedemptionTransaction).
  • Add midnightRedemption.ts with Schedule types and helpers (formatNumber, getRedeemable, getTotal, getStatus).
• Localization/Theme:
  • Add numerous airdrop i18n keys and useStrings hook; update en-US.json.
  • Add illustration_static to light/dark palettes; tweak TopBarLayout overflow to auto.

^{Written by Cursor Bugbot for commit 8861f74. This will update automatically on new commits. Configure here.}

[sonarqube-yoroi]

Quality Gate passed

Issues
16 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

[banklesss]

It seems that the cursor suggestions make sense.

[cursor]

Bug: SVG click detection only catches parent element clicks

The click handler checks if event.target.tagName === 'svg' to detect clicks on the copy icon, but this only works when clicking directly on the SVG element itself. Clicking on child elements inside the SVG (like path, rect, or circle elements) will have a different tagName, causing the check to fail and onSelect() to be called unintentionally when users click on parts of the copy icon.

 

[cursor]

Bug: Error state captured but never displayed to user

The error state is declared and set when getRedemptionTransaction fails, but it's immediately voided with void error and never rendered in the component. When an error occurs, users will see the loading indicator indefinitely with no feedback about what went wrong, since redemptionTxBuildingResponse remains null and the component displays strings.redeemLoading.