-
Notifications
You must be signed in to change notification settings - Fork 36
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
Reading V4 Token #144
Reading V4 Token #144
Conversation
0269245
to
19b9b0e
Compare
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.
lgtm! 233b8ba
Thanks for adding cbor directly to this lib, I've had issues in the past with cbor and server-side rendering, but just tested in a next.js app and works great!
Great to hear that! Please be aware that this implementation is very limited in scope and was only tested against token v4 specific cases. There might be edge cases that are not covered |
FYI this is rebased to the new dev branch and ready for a release in 1.X |
Amazing work, especially implementing the cbor de/serializer. |
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.
ut-LGTM
Fixes: None
Description
This PR changes the way
handleTokens
works. It also adds reading the newly proposed v4 Token format. V4 token are parsed and mapped to output the exact same structure as v3 Token to make handling easier. Consumers ofgetDecodedToken
receive a stable result.Changes
handleTokens
now parses the version and decodes accordingly.PR Tasks
npm run test
--> no failing unit testsnpm run format