Properties from nested mutations not included in response about prisma-binding HOT 9 CLOSED

same problem

from prisma-binding.

@kbrandwijk If I do this I get an error saying I didn't make a subselection for the createUser mutation (Field 'createUser' of type 'User' must have a sub selection). I think the info argument from my signupCompany mutation is incompatible with Prisma's createUser.

from prisma-binding.

A tool that could allow us to easily take information from the info argument of the resolver would be useful on these cases I think. I thought about something like this:

async function myResolver(parent, args, ctx, info) {
  const userInfo = pluck('user', info);
  const user = await ctx.db.mutation.createUser({ ... }, userInfo);
  return { user };
}

I tried searching for a tool like pluck in my example, but failed to find anything. Then I also started studying the info structure to do it myself, but was overwhelmed by its complexity and couldn't put more time into it.

from prisma-binding.

I think just passing through the info argument should work, but I haven't looked at your example in detail.

from prisma-binding.

We'll look into this! 👀

from prisma-binding.

That's an interesting idea @gcangussu. Could you open a new issue for this and elaborate a bit further with a few examples?

from prisma-binding.

same

from prisma-binding.

@schickling I've done this on #118. But with only one example, I will try to add other examples later.

from prisma-binding.

Hey 👋,

guessing the mutations wouldn't make much sense because prisma-binding, even though it serves as a complement to Prisma, isn't tied directly to it in its core implementation.

As @kbrandwijk mentioned, you should find a way to pass down the info parameter. A solution to your problem is implementing AuthPayload which receives the correctly modified info parameter. Check the code I posted below.

const AuthPayload = {
  async user({ user: { id }}, args, ctx: Context, info) {
    return ctx.db.query.user({ where: { id }}, info)
  }
}

Due to inactivity of this issue, I'll close it but feel free to reopen it if you think we should further discuss its content. 🙂

from prisma-binding.