-
Notifications
You must be signed in to change notification settings - Fork 25
feat: Multisig Support #156
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
Conversation
Codecov Report
@@ Coverage Diff @@
## dev #156 +/- ##
==========================================
+ Coverage 83.93% 86.31% +2.38%
==========================================
Files 7 8 +1
Lines 473 592 +119
Branches 104 131 +27
==========================================
+ Hits 397 511 +114
- Misses 69 74 +5
Partials 7 7
Continue to review full report at Codecov.
|
This pull request introduces 1 alert when merging 6ccdc37 into 02ed7c9 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging d9c05bf into 02ed7c9 - view on LGTM.com new alerts:
|
This pull request introduces 1 alert when merging b804467 into 02ed7c9 - view on LGTM.com new alerts:
|
This pull request introduces 6 alerts when merging 1975357 into 02ed7c9 - view on LGTM.com new alerts:
|
This pull request introduces 5 alerts when merging 39e97db into 02ed7c9 - view on LGTM.com new alerts:
|
This pull request introduces 5 alerts when merging 9a843cc into 02ed7c9 - view on LGTM.com new alerts:
|
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.
Only found some minor fixes, a few doubts and JSDocs improvements.
expect(response1.status).toBe(200); | ||
expect(response1.body.success).toBeFalsy(); | ||
|
||
global.config.multisig = TestUtils.multisigData; |
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.
I'm not sure if we must address this topic here, but there is a very small chance that, by playing with global variables, other tests within this same start.test.js
suite may have unintended side-effects.
As our tests need to be independent of each other inside the same suite, a possible solution could be having all these assertions that depend on the global variable within the same it
clause. That way, they would be running deterministically.
Not very readable, but it avoids this small risk.
What do you think?
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.
I think we should improve the way we mock the configuration (using jest mock instead of global), this would solve the problem and wouldn't change the readability of the tests.
A change like this would be better on it's own PR, and since using the global works (at least for now) we can use it like this until we change the configuration mock.
Co-authored-by: Tulio Miranda <[email protected]>
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.
By my side, all approved.
It would be good to define if the CodeCov notifications should be addressed on this PR.
Design
Acceptance Criteria
Create new endpoints as defined on the design:
/multisig-pubkey
/wallet/decode
/wallet/signature
/wallet/partial-tx
/wallet/tx-assemble-push
Security Checklist