feat: support customizing profile and accessToken routes #2451
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
Changes --- - [x] Update the `RoutesOptions` type definition - [x] Update the functions that consume these routes (getAccessToken, useUser) to respect the programmatically configured routes - [x] Update the documentation - [x] Added/updated tests closes auth0#2327
5 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
📋 Changes
RoutesOptionstype definition📎 References
closes #2327
🎯 Testing
In an app that uses @auth0/nextjs-auth0, link to your local clone in the app's package.json as follows:
"@auth0/nextjs-auth0": "file:path/to/nextjs-auth0",wherepath/tois your path to it.I tested this with a local clone with an app that uses @auth0/nextjs-auth0 and everything works as expected.