Hi everyone! Looking at the documentation for 1.17, it feels like Prisma Client is replacing

prisma-binding

. I agree that Prisma Client is a great piece of software and really useful, but I feel like it doesn't apply for the use case where your frontend is using graphql to discuss with your backend. I think that prisma binding is a top notch tool for this kind of use, and therefore should stay in the documentation, next to the Prisma Client. What do you think?

I think they haven't really decided anything. When they released prisma client, it had a

$delegate

method which worked exactly like

prisma-binding

. Then they removed it (4 hours ago!), the official example is using

prisma-binding

for schema delegation. The main problem is that with the new prisma client API, retrieving connections requires a lot of work from the developer (hand-coded resolvers). They hide the

info

object, but without it, it's hard to optimize the queries to only retrieve the necessary fields.

I guess we're supposed to use fragments to retrieve specific fields

Please refer to this message: https://prisma.slack.com/archives/CA491RJH0/p1537357807000100?thread_ts=1537204347.000100&cid=CA491RJH0

Thank you for your work and keeping us informed ❤️