docs: fix incorrect SessionProvider placement in v5 migration guide#13459
Open
Magnuti wants to merge 1 commit into
Open
docs: fix incorrect SessionProvider placement in v5 migration guide#13459Magnuti wants to merge 1 commit into
Magnuti wants to merge 1 commit into
Conversation
The Client Component example called useSession() and then rendered SessionProvider as a descendant of the same component. Since useSession() reads context from an ancestor provider, this throws "useSession must be wrapped in a <SessionProvider />" and contradicts the explanatory text above it. SessionProvider now wraps the tree from a parent layout, consistent with the pattern shown in session-management/get-session.mdx.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
@Magnuti is attempting to deploy a commit to the authjs Team on Vercel. A member of the Team first needs to authorize it. |
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
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.
The "Client Component (App)" example in
migrating-to-v5.mdxcallsuseSession()and then renders<SessionProvider>as a child of that same component.useSession()reads context from an ancestorSessionProvider, so this throws[next-auth]: useSession must be wrapped in a <SessionProvider />at runtime. It also contradicts the explanatory text right above the snippet.This PR splits the example into the client component (just
useSession()) and a root layout that wraps it withSessionProvider, matching the correct pattern already shown indocs/pages/getting-started/session-management/get-session.mdx.