Is there a reason we should discard transaction.mutations?

In every example I can find in the docs you discard the rest of

transaction.mutations

transaction.mutations

and only pick the first element. Is there a reason we don't want to handle the rest?

const todoCollection = createCollection({
  id: "todos",
  onUpdate: async ({ transaction }) => {
    const mutation = transaction.mutations[0]
    await api.todos.update(mutation.original.id, mutation.changes)
  },
})

const todoCollection = createCollection({
  id: "todos",
  onUpdate: async ({ transaction }) => {
    const mutation = transaction.mutations[0]
    await api.todos.update(mutation.original.id, mutation.changes)
  },
})

TanStack•3mo ago•

4 replies

developed-pink

Is there a reason we should discard transaction.mutations?

In every example I can find in the docs you discard the rest of

transaction.mutations

transaction.mutations

and only pick the first element. Is there a reason we don't want to handle the rest?

const todoCollection = createCollection({
  id: "todos",
  onUpdate: async ({ transaction }) => {
    const mutation = transaction.mutations[0]
    await api.todos.update(mutation.original.id, mutation.changes)
  },
})

const todoCollection = createCollection({
  id: "todos",
  onUpdate: async ({ transaction }) => {
    const mutation = transaction.mutations[0]
    await api.todos.update(mutation.original.id, mutation.changes)
  },
})

Is there a reason we should discard transaction.mutations?

Similar Threads

Is there a reason we should discard transaction.mutations?

Similar Threads

Similar Threads

Similar Threads