Fix context.prisma undefined in onConnect (#5407)

keystonejs · Apr 9, 2021 · 76692d2 · 76692d2 · vercel · Apr 9, 2021
1 parent 58a7939
commit 76692d2
Show file tree

Hide file tree

Showing 2 changed files with 8 additions and 1 deletion.
diff --git a/.changeset/silly-numbers-thank.md b/.changeset/silly-numbers-thank.md
@@ -0,0 +1,5 @@
+---
+'@keystone-next/keystone': patch
+---
+
+Fixed a bug where `context.prisma` was `undefined` in the `onConnect()` function.
diff --git a/packages-next/keystone/src/lib/createKeystone.ts b/packages-next/keystone/src/lib/createKeystone.ts
@@ -27,8 +27,10 @@ export function createKeystone(config: KeystoneConfig, prismaClient?: any) {
   const keystone: BaseKeystone = new Keystone({
     adapter,
     queryLimits: graphql?.queryLimits,
+    // We call context.sudo() here to regenerate the `context` object *after* the keystone.connect()
+    // step. This ensures that context.prisma is correctly set up.
     // @ts-ignore The @types/keystonejs__keystone package has the wrong type for KeystoneOptions
-    onConnect: (keystone, { context } = {}) => config.db.onConnect?.(context),
+    onConnect: (keystone, { context } = {}) => config.db.onConnect?.(context?.sudo()),
     // FIXME: Unsupported options: Need to work which of these we want to support with backwards
     // compatibility options.
     // defaultAccess