-
Notifications
You must be signed in to change notification settings - Fork 61
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
Bypass for InResponseTo #87
Conversation
# Conflicts: # package-lock.json # package.json # test/tests.spec.ts
…rch and take one that is valid (checkTimestampsValidityError). But what if we don't have any valid sc? Take the first one; it will fail later in the flow.
…rmation is found then the firs one in the resulting array of valid confirmations is to be used, if none is found undefined is returned.
…Add one more test to check if second subjectconfirmation is valid since the first one is expired.
…something that seems wrong in having two tests that should be equals in execution pretend to validate two different assertions
I was just about to review this code when I noted that there are merge conflicts. Can you please resolve these before I review the code? |
Codecov Report
@@ Coverage Diff @@
## master #87 +/- ##
==========================================
+ Coverage 79.04% 79.14% +0.10%
==========================================
Files 12 12
Lines 792 796 +4
Branches 238 238
==========================================
+ Hits 626 630 +4
Misses 73 73
Partials 93 93
Continue to review full report at Codecov.
|
Sorry for the delay; I miss my duties on doing this merge sorry Chris. If I could do something more let me know; Really, I'm sorry about my fault. |
@cjbarth sorry, maybe I forgot to mention you. Could you please take a look on this? |
Description
This should adress correctly the case of zero or more subjectconfirmations. If any is valid should go trough check for in-responseto or a fail condition is if there are some and none is vaid for any reason.
Checklist:
InResponseTo
Assertion Validation #82 ]