Problem: (CRO-518) HD and Basic wallet code is not separated out#532
Problem: (CRO-518) HD and Basic wallet code is not separated out#532bors[bot] merged 1 commit intocrypto-com:masterfrom devashishdxt:cleanup
Conversation
Solution: Separated HD wallet code in `HdKeyService`
Codecov Report
@@ Coverage Diff @@
## master #532 +/- ##
==========================================
- Coverage 67.37% 67.16% -0.22%
==========================================
Files 120 122 +2
Lines 14077 14070 -7
==========================================
- Hits 9485 9450 -35
- Misses 4592 4620 +28
|
tomtau
left a comment
There was a problem hiding this comment.
I don't have enough context for this problem, but for the HD wallet code common for client-cli/rpc that can be exposed in a library, would it make sense to move it to client-common?
| use client_common::{Error, ErrorKind, Result}; | ||
| use client_core::WalletClient; | ||
| use quest::{ask, success}; | ||
| use bip39::{Language, Mnemonic}; |
There was a problem hiding this comment.
should this functionality be here, as it'll be needed in client-rpc + if the client-* is exposed as a library?
There was a problem hiding this comment.
I don’t think HD wallet code can be moved to client-common because it works with other parts in client-core. One possible change is to return SecUtf8 instead of Mnemonic when creating a new wallet so that we can remove bip39 dependency from client-cli and client-rpc.
@leejw51crypto Any comments?
There was a problem hiding this comment.
changing to SecUtf8 makes sense
|
bors r+ |
|
bors is pending |
Solution: Separated HD wallet code in
HdKeyService