fix: use NEXT_PUBLIC_PROFILE_ROUTE in Auth0Provider #1966
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
Similar to what's done in
useUser
, first checkprocess.env.NEXT_PUBLIC_PROFILE_ROUTE
and fallback to"/auth/profile"
when setting thefallback
data for the profile route.📎 References
Fixes #1965
🎯 Testing
NEXT_PUBLIC_PROFILE_ROUTE
environment variable. (ex:NEXT_PUBLIC_PROFILE_ROUTE=/api/me
.Auth0Provider
:useUser()
hook to retrieve the user and render a field, such as thesub
:sub
is immediately visible on the screen and that there isn't a brief period where "undefined" is first shown.