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
Ledger integration milestone 2 #137
Comments
Please can you include motivation behind those desired changes? Based on that list alone I'm confident this would be going three steps backwards. So here are some comments regarding the items about why they are as they are.
The
The main reason why the Channel abstraction exists is to make UI layer code a lot simpler to deal with. You create a channel for a component and when that component gets destroyed you simply close that channel, you don't have to worry about the pending async tasks as the LedgerHub takes care of disposing of them cleanly.
But it already is: https://github.com/RiseVision/rise-react-wallet/blob/master/src/stores/ledger.ts#L150 (it propagates through via the getters in
I'm pretty confident you cannot replace promises with async and get codebase that's easier digest than the current one. The executioner needs to be able to trigger the start of a Ledger task and inject the ping task into the queue. Without promises that isn't really possible. Currently async is used where promises aren't absolutely necessary. |
- bind ledger communication to the open/close events - unify naming of the transaction dialog
I will provide detailed info once I assign the ticket and start working on it. Overall the implementation seems too complex, not encapsulated enough and ideally we'd depend on some external module(s).
I'm pretty convinced store & hub can be merged for now.
Could be simplified from the consumer perspective.
Not in the store, which is the point of @observables.
Theres nothing wrong in going backwards to simplify things, as long as they work equally well. Also, blocked by #121. |
Ledger things have undergone a refactor, so closing this issue. |
Ledger's refactoring was related to supporting I've updated the todo list in the ticket's description to reflect the current situation. |
- fix ConfirmationDialog for ledger (goBack) - fix transaction entry key for unconfirmed txes
- fix ConfirmationDialog for ledger (goBack) - fix transaction entry key for unconfirmed txes
Next milestone for the ledger integration should include:
LedgerStore
andLedgerHub
LedgerChannel
in favor ofLedgerStore.isOpen
deviceId
should be an observableThe text was updated successfully, but these errors were encountered: