-
-
Notifications
You must be signed in to change notification settings - Fork 151
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
New screen: On-chain addresses #2242
Conversation
e712673
to
bd7e3ca
Compare
We gotta change the icon. Currently it's credit cards? |
We need to configure this for Lightning Node Connect and Embedded LND as well |
This view should also probably just replace the current |
Lastly, we should think about adding the ability for users to pick the account they want to generate addresses for |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
see comments above
I think the sections should be collapsible (perhaps by default) - that way users will be able to navigate more easily if they have a ton of addresses |
views/OnChainAddresses.tsx
Outdated
|
||
private loadAddresses = async () => { | ||
this.setState({ loading: true }); | ||
const listAddressesResponse = await BackendUtils.listAddresses(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we should probably move this call to the UTXOsStore
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also, I think this is problematic. Fetching all addresses at once can lead to timeouts on nodes that have a bunch generated. Instead, I think it would be better to fetch the accounts list and then fetch the addresses for each account, one at a time.
We'd have to refactor quite a bit, but I don't think things will hold up as is.
after giving some thought to this, I think if In keeping in sync with the Coins button under the On-chain balance slider, we should label the button on the Menu view |
bd7e3ca
to
a4a895c
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-09-26.at.17.03.06.mp4
I think hide 0-balance should not remove the complete view in case we only have o-balance addresses
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Simulator.Screen.Recording.-.iPhone.15.Pro.-.2024-09-26.at.17.10.42.mp4
the view glitch when we tap to add
I think we need a separate issue for this. Mind filing one? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can track the issue here #2441 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
tACK
Description
This adds "On-chain addresses" to the menu:
This displays all addresses from LND's ListAddresses grouped by account and address type. Allows hiding 0-balance addresses and sorting by creation time and balance.
This pull request is categorized as a:
Checklist
yarn run tsc
and made sure my code compiles correctlyyarn run lint
and made sure my code didn’t contain any problematic patternsyarn run prettier
and made sure my code is formatted correctlyyarn run test
and made sure all of the tests passTesting
If you modified or added a utility file, did you add new unit tests?
I have tested this PR on the following platforms (please specify OS version and phone model/VM):
I have tested this PR with the following types of nodes (please specify node version and API version where appropriate):
Locales
Third Party Dependencies and Packages
yarn
after this PR is merged inpackage.json
andyarn.lock
have been properly updatedOther: