-
Notifications
You must be signed in to change notification settings - Fork 71
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
Add VerifierAlgorithm for ES256 #249
Conversation
…p into files by curve
…les as suggested by linter
…ithms, add a not for secp256r1 support of in src/VerifierAlgorithm.common.ts
…ted for u8a, temporarily commiting for now
to match upstream
… with secp256k1 not secp256r1
I should note that I am making progress with JWT.ts and JWT.test.ts. This may be relevant to the VerifierAlgorithm.ts. Maybe we should wait for that? |
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.
This looks great, thanks for the contribution!
Don't concern yourself too much with refactoring. While that is very important, I'd like to separate any refactoring changes from feature implementations. If you do want to contribute refactoring PRs, please separate code-refactoring-PRs from test-refactoring-PRs to ease the review. Thank you for coming back with small PRs, it makes this process so much easier! |
# [6.8.0](6.7.0...6.8.0) (2022-09-06) ### Features * add VerifierAlgorithm for ES256 ([#249](#249)) ([05283ac](05283ac))
🎉 This PR is included in version 6.8.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This is the answer to:
#248 (review)
Update VerifierAlgorithm.ts for ES256.
Update VerifierAlgorithm.test.ts for ES256.
I had to re-declare some variables locally for ES256. Is it appropriate to move some globally declared variables for ES256K and ed25519 or just leave them?