-
-
Notifications
You must be signed in to change notification settings - Fork 126
Use async/await instead of then #148
Conversation
mcmire
left a comment
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.
Good idea! Had some suggestions.
| * Returns the currently initialized keyring that manages | ||
| * the specified `address` if one exists. | ||
| * | ||
| * @param {string} address - An account address. |
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.
Nit: There is a .then a few lines up from here in getAccounts that we can remove as well
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.
Great work @darkwing ! This has been on my wishlist for a long time. A few suggestions but everything looks good
Co-authored-by: Elliot Winkler <elliot.winkler@gmail.com>
ryanml
left a comment
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.
awesome!
Gudahtt
left a comment
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.
LGTM!
A new vault should be unlocked after being created, because the password is submitted as part of creating the vault. This was accidentally broken as part of #148. A unit test has been added to ensure this doesn't happen again.
A new vault should be unlocked after being created, because the password is submitted as part of creating the vault. This was accidentally broken as part of #148. A unit test has been added to ensure this doesn't happen again.
Much easier to read than the mess of
then's.