add getCustomClaims and useCustomClaims hook #254
Merged
Conversation
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
ericroberts
approved these changes
May 27, 2025
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.
This pull request introduces functionality to extract and handle custom claims from access tokens, along with corresponding tests and updates to the codebase. The key changes include the addition of the
getCustomClaimsfunction, a newuseCustomClaimsReact hook, and unit tests to ensure proper behavior.New functionality for custom claims:
getCustomClaimsfunction: Added a utility function insrc/session.tsto extract custom claims from a JWT while filtering out standard claims. This function supports both direct access token input and session-based token retrieval.useCustomClaimshook: Introduced a React hook insrc/components/useCustomClaims.tsto provide custom claims in React components by decoding the access token and excluding standard claims.Fixes #253
Fixes #235