We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
N/A
The current code snippet for migrating nextauth to JWT strategy is outdated to what is scaffolded.
Current snippet:
export const authOptions: NextAuthOptions = { + session: { + strategy: "jwt", + }, callbacks: { - session({ session, user }) { + session({ session, token }) { - if (session.user) { + if (session.user && token.sub) { - session.user.id = user.id; + session.user.id = token.sub; } return session; } }, };
However, currently T3 uses a destructuring approach for the Callback object, like so:
session: ({ session, token }) => ({ ...session, user: { ...session.user, id: token.sub, }, }),
https://create.t3.gg/en/usage/next-auth#usage-with-nextjs-middleware
No response
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
Provide environment information
N/A
Describe the bug
The current code snippet for migrating nextauth to JWT strategy is outdated to what is scaffolded.
Current snippet:
export const authOptions: NextAuthOptions = { + session: { + strategy: "jwt", + }, callbacks: { - session({ session, user }) { + session({ session, token }) { - if (session.user) { + if (session.user && token.sub) { - session.user.id = user.id; + session.user.id = token.sub; } return session; } }, };However, currently T3 uses a destructuring approach for the Callback object, like so:
Reproduction repo
https://create.t3.gg/en/usage/next-auth#usage-with-nextjs-middleware
To reproduce
N/A
Additional information
No response
The text was updated successfully, but these errors were encountered: