CODEWITHSUNDEEP
graphqlprismaprisma-graphqlnexus-prisma
Trufa
Trufa

Reputation: 40717

How to do a nested mutation resolver with nexus-prisma

I have the following datamodel:

type Job { 
    // ...
    example: String
    selections: [Selection!]
    // ...
}

type Selection { 
    ...
    question: String
    ...
}

I define my object type so:

export const Job = prismaObjectType({
  name: 'Job',
  definition(t) {
    t.prismaFields([
      // ...
      'example',
      {
        name: 'selections',
      },
      // ...
    ])
  },
})

I do my resolver this way:

t.field('createJob', {
  type: 'Job',
  args: {
    // ...
    example: stringArg(),
    selections: stringArg(),
    // ...
  },
  resolve: (parent, {
    example,
    selections
  }, ctx) => {
    // The resolver where I do a ctx.prisma.createJob and connect/create with example
  },
})

So now in the resolver I can receive the selections as json string and then parse it and connect/create with the job.

The mutation would look like this:

mutation {
  createJob(
    example: "bla"
    selections: "ESCAPED JSON HERE"
  ){
    id
  }
}

I was wondering if there's anything more elegant where I could do something like:

mutation {
  createJob(
    example: "bla"
    selections: {
       question: "bla"
    }
  ){
    id
  }
}

or 

mutation {
  createJob(
    example: "bla"
    selections(data: {
      // ...
    })
  ){
    id
  }
}

I've noticed that with nexus-prisma you can do stringArg({list: true}) but you can't really do objects.

My main question is what is the most elegant way to do either nested mutation or connect all in one.

Upvotes: 4

Views: 3503

Answers (1)

Daniel Rearden
Daniel Rearden

Reputation: 84667

You can use an inputObjectType as shown in the docs:

export const SomeFieldInput = inputObjectType({
  name: "SomeFieldInput",
  definition(t) {
    t.string("name", { required: true });
    t.int("priority");
  },
});

Make sure to include the type as part of the types you pass to makeSchema. You can then use it to define an argument, like

args: {
  input: arg({
    type: "SomeFieldInput", // name should match the name you provided
  }),
}

Now, the argument value will be available to your resolver as a regular JavaScript object, not a String. If you need a list of input objects, or want to make the argument required, you do so using the same options you would provide with when using a scalar -- list, nullable, description, etc.

Here's a complete example:

const Query = queryType({
  definition(t) {
    t.field('someField', {
      type: 'String',
      nullable: true,
      args: {
        input: arg({
          type: "SomeFieldInput", // name should match the name you provided
        }),
      },
      resolve: (parent, { input }) => {
        return `You entered: ${input && input.name}`
      },
    })
  },
})

const SomeFieldInput = inputObjectType({
  name: "SomeFieldInput",
  definition(t) {
    t.string("name", { required: true });
  },
});

const schema = makeSchema({
  types: {Query, SomeFieldInput},
  outputs: {
    ...
  },
});

Then query it like:

query {
  someField(
    input: {
       name: "Foo"
    }
  )
}

Or using variables:

query($input: SomeFieldInput) {
  someField(input: $input)
}

Upvotes: 5

Related Questions