-
-
Notifications
You must be signed in to change notification settings - Fork 184
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
feat: expand allowed removeKeyHash length from exactly 32 to 16-32 #248
feat: expand allowed removeKeyHash length from exactly 32 to 16-32 #248
Conversation
Change looks good, but we'll need a test added to approve it. |
9dcf5fe
to
8101586
Compare
Cool, I've added a test, don't have any experience with ava so let me know if something should be changed ✌🏼 No idea why the existing test would start failing on Node 10, maybe you know/can rerun the job? |
Click on the |
I got that part but it's failing on the existing test (which I haven't touched), not on the test I've added, unless I'm misinterpreting the output? |
Ping @shellscape, sorry to bother you but I wanted to make clear that I need your help to finish this up 😅 |
So the way the output reads, the test for the |
10efa33
to
3eeac03
Compare
Codecov Report
@@ Coverage Diff @@
## master #248 +/- ##
=======================================
Coverage 98.19% 98.19%
=======================================
Files 3 3
Lines 111 111
=======================================
Hits 109 109
Misses 2 2 Continue to review full report at Codecov.
|
3eeac03
to
f589030
Compare
f589030
to
301c595
Compare
Apparently the test output was incorrect, deleting it and letting it regenerate solved the problem. Couldn't test it locally so had to use the GH action a bunch of times. |
This PR contains:
Are tests included?
Breaking Changes?
If yes, then include "BREAKING CHANGES:" in the first commit message body, followed by a description of what is breaking.
List any relevant issue numbers:
Description
As discussed in #241.