Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
[LWD] feat(tracking): add tracking contact send flow lwd #21465
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: develop
Are you sure you want to change the base?
Uh oh!
There was an error while loading. Please reload this page.
[LWD] feat(tracking): add tracking contact send flow lwd #21465
Changes from all commits
cb2caecFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
Check failure on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
SendHeader › keeps the recipient field read-only on the amount step
Check warning on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
RETRY 1: SendHeader › keeps the recipient field read-only on the amount step
Check failure on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
SendHeader › uses the placeholder computed by the header model on the recipient step
Check warning on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
RETRY 1: SendHeader › uses the placeholder computed by the header model on the recipient step
Check failure on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
SendHeader › goes back to the recipient step when clicking the header showing a plain address
Check warning on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
RETRY 1: SendHeader › goes back to the recipient step when clicking the header showing a plain address
Check failure on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
SendHeader › goes back to the recipient step when clicking the header showing a contact
Check warning on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
RETRY 1: SendHeader › goes back to the recipient step when clicking the header showing a contact
Check failure on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
SendHeader › falls back to the address input when the recipient is not a contact
Check warning on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
RETRY 1: SendHeader › falls back to the address input when the recipient is not a contact
Check failure on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
SendHeader › shows the contact avatar and name when the recipient is a contact
Check warning on line 158 in apps/ledger-live-desktop/src/mvvm/features/Send/components/SendHeader.tsx
RETRY 1: SendHeader › shows the contact avatar and name when the recipient is a contact
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.