Skip to content

Send Screen Redesign#115

Open
notTanveer wants to merge 9 commits into
CypherCommons:masterfrom
notTanveer:feat/send-redesign
Open

Send Screen Redesign#115
notTanveer wants to merge 9 commits into
CypherCommons:masterfrom
notTanveer:feat/send-redesign

Conversation

@notTanveer

@notTanveer notTanveer commented Jun 4, 2026

Copy link
Copy Markdown
Contributor

Revamp Send Screen

Send Screen Screenshot 1 Send Screen Screenshot 2 Send Screen Screenshot 3
Send Screen Screenshot 4 Send Screen Screenshot 5 Send Screen Screenshot 6

@notTanveer notTanveer marked this pull request as draft June 4, 2026 18:52
@notTanveer notTanveer force-pushed the feat/send-redesign branch 2 times, most recently from d03ffbf to 3030a4d Compare June 6, 2026 13:36
@notTanveer notTanveer marked this pull request as ready for review June 9, 2026 09:28
Comment thread screen/send/Confirm.tsx Outdated
@chaitika

Copy link
Copy Markdown
Contributor

i can see verbose comments at multiple places. would suggest to keep them only if explicitly needed, and avoid over-explanation

@chaitika

Copy link
Copy Markdown
Contributor

the Nextbutton width sizes are visibly different in send details screen and set fee screen; should be coherent.

log-49 log-48

@chaitika

Copy link
Copy Markdown
Contributor

is the allowed unit to enter amount only btc, or should it be both btc <-> sats ?

on sendDetails screen amount can be entered in "btc" units only.
imo, we should keep "sats" also as a unit.

@notTanveer

Copy link
Copy Markdown
Contributor Author

is the allowed unit to enter amount only btc, or should it be both btc <-> sats ?

on sendDetails screen amount can be entered in "btc" units only.
imo, we should keep "sats" also as a unit.

as per the new design, we can only change the unit from the settings. please post this in figma, lets see what matt and anmol has to say

Comment thread screen/send/Confirm.tsx Outdated
Comment thread components/themes.ts
Comment thread screen/send/SendDetails.tsx Outdated
Comment thread components/icons/ScanQRIcon.tsx Outdated
Comment thread screen/send/Confirm.tsx Outdated
Comment thread screen/send/SendDetails.tsx Outdated
notTanveer added a commit to notTanveer/silent-pay-wallet that referenced this pull request Jun 11, 2026
- Remove dead HeaderRightButton memo in Confirm; simplify setOptions
  effect to [setOptions] dep only
- Drop redundant String() wrap on satoshiToBTC() in Confirm
- Collapse unreachable addresses.length > 1 branch in SendDetails;
  remove details_recipient_title loc key
- Fix editable AmountHero when Max active: pass '' so editing starts
  from a blank field
- Make ScanQRIcon color prop required (drop hardcoded '#754CE8' default)
- Fix themes.ts comment: dark mode is not wired up, not "inherits via spread"
@notTanveer notTanveer force-pushed the feat/send-redesign branch 2 times, most recently from b7b86f3 to 5e9f5c8 Compare June 15, 2026 06:33
Comment thread components/icons/CheckmarkIcon.tsx Outdated
@theanmolsharma

Copy link
Copy Markdown
Collaborator

@notTanveer please fix the E2E tests

isScanActive() was removed from HDSilentPaymentsWallet in bfac4ef while
the isScannable() runtime guard still required it, so isScannable() returned
false for every wallet. That silently broke two things:

- deleteWallet skipped wallet.cancelScan() (gated behind the guard), so a
  deleted wallet's scan loop + polling kept running and a re-import started a
  second concurrent scan.
- useScannableWallet returned null and the scan-state callback was never
  wired, so the WalletList progress bar never rendered.

Since the app is single-wallet-type (TWallet = HDSilentPaymentsWallet, and
deserialization rejects all other types), drop the IScannableWallet interface
and isScannable() guard entirely and call the scan methods directly on the
concrete wallet. This makes every scan call site compile-checked, so removing
one of these methods now fails tsc instead of failing silently at runtime.

Add a unit test asserting the wallet still exposes the scan-control surface.
@notTanveer notTanveer force-pushed the feat/send-redesign branch from 7072c82 to d0646be Compare June 24, 2026 08:06
@notTanveer notTanveer force-pushed the feat/send-redesign branch from a95182f to 1e9a997 Compare June 24, 2026 09:06
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.

3 participants