why do we add prisma in ctx instead of using import ?

As stated in the doc

We include the Prisma Client in Context by default and recommend using this instead of importing it separately in each file.

We include the Prisma Client in Context by default and recommend using this instead of importing it separately in each file.

We include the Prisma Client in Context by default and recommend using this instead of importing it separately in each file.

We include the Prisma Client in Context by default and recommend using this instead of importing it separately in each file.

but there is no explanation
Why is it better ?
What is the difference ?

techblooded•4/27/23, 7:36 PM

It’s mainly so u dont have to setup and initialize prisma or import it in every router. Instead the ctx option allows keeping all these sort of things shared.

GlorrinOP•4/28/23, 12:57 PM

Ok but if my routers become more complexe and I want to externalise it in services files, can I import it there or should I "drill prop" prisma in ctx ?

Ramazan•4/28/23, 5:25 PM

Could you give an example of what you mean?

GGlorrin Ok but if my routers become more complexe and I want to externalise it in servic...

techblooded•4/28/23, 10:57 PM

i think the ctx is exposed to make it easier group up such shared services in one place, but there isn't any requirement to use it. i would say that the better way would be ctx because that way u dont have dup imports

cje•4/29/23, 5:04 AM

its done this way so that you know you have the same instance in every procedure, better dx of having it on ctx, and lets you monkeypatch it for testing

cje•4/29/23, 5:04 AM

but in terms of just the procedure itself it doesn't make a difference