Improve docs on Fragments, how exactly is it working

Hey, so I am relying on data from the database to verify certain fields, so it seems using fragments would be beneficial for my use case. However I am not really sure how they work or what they do.

So there is this in the docs:

const isItemOwner = rule({
  cache: 'strict',
  fragment: 'fragment ItemID on Item { id }',
})(async ({ id }, args, ctx, info) => {
  return ctx.db.exists.Item({
    id,
    owner: { id: ctx.user.id },
  })
})

Does it provide a way to cache the data you get from the Item query or what is it doing here?

Also why are you getting id from the parent argument and not from args ? I would be happy if I could get some explanation of how exacyly fragments work together with graphql-shield.

(I know what fragments in general are, (I think))

[maticzav]

https://github.com/maticzav/gimb-events/blob/master/server/src/shield.ts

Hope that helps.

[chrisknuteson-qumulex]

@maticzav That does, thank you. I’ve been using prisma-client (which doesnt support the fragment option) and need to investigate switching over to the prisma-binding (which does)