I'm trying to migrate a pet project to use the prisma client instead of

prisma-binding

. A few questions: - My resolvers use

fragment:

props. Should I import

extractFragmentReplacements

from

graphql-binding

from now on? - I'm using typescript and

prisma.user({ id: userId }).$fragment(fragment)

seems to return

{}

. What am I doing wrong? (

fragment

is a string) - Is it possible to pass the

info

to the prisma query in order to retrieve connections? The $delegate seems to be gone from

prisma

. - Is there a 1.16 => 1.17 migration guide?

Those are awesome questions. Could you raise 1) and 2) in individual forum discussions? 3)

$delegate

has been removed from Prisma Client. For schema delegation, you can use

prisma-binding

. We will provide more clarity about this decision here soon: https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394?u=nilan 4) There is no

1.16

=>

1.17

migration guide yet. Besides

prisma generate

, which is a new feature, and a very specific breaking change for the generated schema, there are no changes that justify a specific migration guide. Were you actually asking for a

prisma-binding

to Prisma Client migration guide?