Allow passing prisma client settings

[jasonkuhrt]

Perceived Problem

• It is not possible to configure the options passed to the prisma client constructor
• It is not possible to construct the prisma client oneself

Ideas / Proposed Solution(s)

• Allow passing prisma client options through the prisma plugin constructor

   use(prisma({ clientOptions: { ... }) })

[jasonkuhrt]

Use-case for this occurred in https://www.youtube.com/watch?v=YQe3yOYPRvc.

[schickling]

Wouldn't it make more sense for people to pass in a Prisma Client instance instead of config options? Feels more transparent and idiomatic to me.

[jasonkuhrt]

How about

 use(prisma({ client: PrismaClient | { options: PrismaClientOptions }) })

Examples

use(prisma())

import { PrismaClient } from 'nexus-plugin-prisma/client'

use(prisma({ client: new PrismaClient() }))

use(prisma({ client: { options: { ... }}})))

or maybe the we can elide the options level

use(prisma({ client: { ... }})))

Related to passing prisma client instances: #465

I think we should maintain zero config.

Instance discussion brings into conversation other discussions about project dependencies and/or prisma client class access.

[schickling]

That works for me. Also related issue: https://github.com/prisma/prisma-client-js/issues/535

[emroot]

This would be great!
Definitely needed for me to move from schema to next

[jasonkuhrt]

@emroot good to know! We do look at the number of 👍's so add yours!

[jasonkuhrt]

@Weakky discovered the poor autocomplete story:

abstract example of the problem: https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=11&pc=24#code/MYGwhgzhAEBiD29oG8CwAoa0wC5oQBcAnASwDsBzaAXmgHI6MsAjPMgVwFtmBTIm6AEYMAXwwYCATwAOPaACEw-WmkzQAXnkKlKTaAA82XXkVHj0U2dACCAhEgA+CpeeDwyhbHlsqx6IA

We agreed therefore to go with this API:

// union type, either works:

use(prisma({ client: { options: ... }) })
use(prisma({ client: { instance: ... }) })

[Weakky]

Feature implemented in graphql-nexus/nexus-plugin-prisma#105
Available on nexus-plugin-prisma@next 👍

[schickling]

@Weakky is this documented already?