Test transactions & address management #133
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- created sub-folders to group related pages (e.g. design system). - moved contacts and silent payment pages to milestone 1.8 -
|
Nice work. Can you please make the following tweaks?
I'd also keep the test transactions feature out of the send milestones. It's more like a concept at this stage, like some of the other stuff at the bottom of the sidebar menu. We could put all those future ideas in a separate sub-category (but as I mentioned above, restructuring pages is not purpose of this PR). |
|
Thanks for taking a look. Worked on the suggested tweaks. |
rabbitholiness
changed the title
rabbitholiness
changed the title
Merged
GBKS
approved these changes
Jan 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR adds a page for a dedicated user flow for automated test transactions for high-value transactions. The original idea is covered in this issue. The design is conceptually done and ready for review (Figma). What's missing so far are mobile screens.
It also adds a page with design concepts for how users might view and manage wallet addresses, including silent payment addresses. Detailed interactions and flows need to be fleshed out, but conceptual feedback would be nice. Especially managing silent payment sub-addresses (a.k.a. labels) will be more complex.