New "many" mutations: `updatePosts` / `createPosts`

Currently we have these:

Singular	Many
createPost	❌
Post	allPosts
updatePost	❌
deletePost	deletePosts

The missing mutations would be createPosts & updatePosts to complete that table.

The input parameters would be the same for the Many case as for the Singular case, but as an Array (and likewise for the return type):

input PostsUpdateInput {
  id: ID!
  data: PostUpdateInput
}

input PostsCreateInput {
  data: PostCreateInput
}

type Mutation {
  updatePosts(data: [PostsUpdateInput]): Posts
  createPosts(data: [PostsCreateInput]): Posts
}

Which you’d then execute like so:

mutation {
  createPosts(data: [
    { data: { title: "Hello" } },
    { data: { title: "A post" } }
  ]) {
    id
    title
  }
}

mutation {
  updatePosts(data: [
    { id: "abc123", data: { title: "Hello" } },
    { id: "def456", data: { title: "A post" } }
  ]) {
    id
    title
  }
}

[timleslie]

I’m +1 on this idea. I think the deleteMutation and deleteManyMutation methods on the List class give us the pattern for how to implement these mutations.

At the moment the deletePosts mutation runs each of the delete operations independently, so even if one fails for some reason (e.g. validation), the others still get deleted. This is by design and is believed to be correct.

[maheraldous]

I just started using Keystone and when I use this code below in the image, it work and create one user but as long I use the second code it won’t work

https://prnt.sc/u97b18

https://prnt.sc/u97bmq