Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | fix cancelTransaction not reciving a callback | frankiebee | 2017-08-04 | 1 | -1/+2 |
| | |||||
* | Fix test to match behavior | frankiebee | 2017-07-13 | 1 | -1/+1 |
| | |||||
* | use new nodeify | frankiebee | 2017-07-13 | 1 | -21/+6 |
| | |||||
* | Add useful nodeify error message | Dan Finlay | 2016-11-30 | 1 | -2/+9 |
| | | | | | | | If a nodified method does not return a Promise, it will throw an error, like this: ``` Error in event handler for (unknown): Error: The function setSelectedAccount did not return a Promise, but was nodeified. ``` | ||||
* | Fix nodeify | Dan Finlay | 2016-11-29 | 1 | -55/+13 |
| | |||||
* | Denodeify most of KeyringController | Dan Finlay | 2016-11-29 | 1 | -0/+59 |
Mostly Fixes #893 A couple methods cache callbacks, and will require a larger refactor to fully denodeify. Specifically, our methods involving web3 requests to sign a tx, sign a message, and approve or cancel either of those. I think we should postpone those until the TxManager refactor, since it will likely handle this response caching itself. |