Are input types inherently broken? I used the SDL converter and I am getting this error: Could not find argument username for type User Prisma Playgrounds autocompletes username in the variables section thought. I thought it was my code at first, but now the SDL generated code is throwing the same fit.

cc @tgriesser

Is there a link to code anywhere to see what’s going on?

I don’t see anything wrong with the input types on nexus’ end… just ran your branch (without prisma) with :

mutation {
  createUser(data: {username: "Something", password: "Something Else"}) {
    id
  }
}

and changed the resolve of

createUser

to:

resolve(root, args, ctx) {
  const { data } = args;
  console.log(args);
  return { id: 1 };
}

and I see

{ data: { username: 'Something', password: 'Something Else' } }

in the console, so the input types seem to be working fine there. Maybe it’s something in the translation to prisma’s end? @weakky any idas here?

Hey, could you please share the stacktrace? We can’t know where’s the problem coming from with such a little input 😕

Here is the error message I get. I will also post my screen from playground.

Yeah so that’s an issue with the generated resolvers in

nexus-prisma

. Does your

User

type in your datamodel looks like this?

type User {
  id: ID! @unique
  username: String! @unique
}

No it looks like type User { id: ID! @unique username: String! password: String! posts: [Post!]! }

Are you sure you have a properly generated

prisma-client

?

yes

The issue is for sure not on

nexus-prisma

side, you must have an issue with your prisma-client not being properly generated

I completely did a git clone and set everything up. Create mutations work, queries don't work, but only when you provide arguments. If you have an empty where object it will work, but that is not useful.