Correct decodeToken behavior#1877
Merged
Merged
Conversation
evanugarte
force-pushed
the
Adarsh/decodeToken
branch
from
October 11, 2025 20:59
ea6335d to
2f2f961
Compare
evanugarte
force-pushed
the
Adarsh/decodeToken
branch
from
October 11, 2025 21:20
e26efc6 to
632b57c
Compare
evanugarte
approved these changes
Oct 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
we don't really need any token functions besides
decodeTokento check ifso we can delete all other token functions and absorb them into
decodeToken