From aa6d7084c5bb83d31d9356d2da63c8c0b372198f Mon Sep 17 00:00:00 2001 From: Bereket Engida Date: Wed, 20 Nov 2024 15:15:54 +0300 Subject: [PATCH] chore: update next auth migration guide --- docs/content/docs/guides/next-auth-migration-guide.mdx | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/content/docs/guides/next-auth-migration-guide.mdx b/docs/content/docs/guides/next-auth-migration-guide.mdx index ed607710..6052c1e7 100644 --- a/docs/content/docs/guides/next-auth-migration-guide.mdx +++ b/docs/content/docs/guides/next-auth-migration-guide.mdx @@ -67,14 +67,14 @@ In this guide, we’ll explore how to seamlessly transition a project from Next }); ``` - **NOTE:** If you're using orm adapters, you can also map the fields in the adapter like + **NOTE:** If you're using orm adapters, you can also map the fields in your schema file **Example with Prisma** ```prisma title="schema.prisma" model Session { id String @id @default(cuid()) expires DateTime @map("expiresAt") // Map expires to your existing expires field // [!code highlight] - token String @@map("sessionToken") // Map token to your existing sessionToken field // [!code highlight] + token String @map("sessionToken") // Map token to your existing sessionToken field // [!code highlight] userId String user User @relation(fields: [userId], references: [id]) }