-
Notifications
You must be signed in to change notification settings - Fork 3
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: new error handling #10
Conversation
This pull request introduces 1 alert when merging 78fb8cc into da9f954 - view on LGTM.com new alerts:
|
test/verify.v3.test.ts
Outdated
@@ -98,7 +98,7 @@ describe("verify", () => { | |||
expect(isValid(results)).toStrictEqual(false); | |||
expect(isValid(results, ["DOCUMENT_INTEGRITY", "DOCUMENT_STATUS"])).toStrictEqual(true); | |||
}); | |||
it("should fail for when identity is invalid and be valid for remaining checks when document with certificate store is valid on ropsten", async () => { | |||
it("should fail for when identity is invalid and be valid for remaining checks when document with certificate store is valid on ropsten", async () => { |
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.
remove for in should fail for
?
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.
ah i missed this, it's fixed in a3b65bb. yep we should remove the "for"
This pull request introduces 1 alert when merging 3c5a1fb into da9f954 - view on LGTM.com new alerts:
|
🎉 This PR is included in version 2.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
todo
github:Open-Attestation/oa-verify#feat/new-errors
oa-verify
refer to Open-Attestation/oa-verify#110 for the full changelog