hi im new with graphql prisma client doesnt allow info object? i was using prisma before and used to allow it, any doc reference for this? this affect bringing data from prisma to grapql-yoga? ex: instead of bringing from pisma user: {name} bringing all the user object

I got really confused when I first encountered this as well. But as far as I've understood there are two ways to work with Prisma, through the

prisma-client

and

prisma-binding

. The Prisma client is a more traditional ORM replacment like sequalize/mongoose, etc. While the

prisma-binding

behaves like a graphql server, taking in the info object, etc. The client works well for any scenario in any language, but you have to resolve children yourself. While the binding is best for JS based graphql servers, where your API is tightly coupled with the database structure. – If I've understood it correctly, I just switched my project from client to binding myself. REF: https://www.prisma.io/forum/t/help-understanding-prisma-clients-value-proposition/4394/14

thanks a lot yes i worked with bindings with the boilerplate the first time and now is the client got confused also

I think the documentation needs some work to clarify this. It has a page about it, but it's using a wording which is not easy to grasp when which method is best and that they are both viable options.