Sorry for all the questions - I’m just really confused. Do I really need to re-create the entire API with yoga? Is there no way to expose the prisma API to the client while still adding auth? I just want the auto-generated API because it’s really nice, but I feel like I get none of that benefit once I put yoga infront of it

If you really want to expose the entire Prisma API 1-1 without any changes or modifications, then a simple authentication layer is already enough. As soon as you want to transform operations from the Prisma schema into your application schema (and maybe even merge it together with other GraphQL schemas), you are entering schema stitching land, where

forwardTo

comes in.

That reminds me…I need to add some docs on

forwardTo

, so you might find it somewhat lacking as of right now 😕

@devan https://github.com/graphql-binding/graphql-binding/issues/14