invalidateQueries / refetchQueries / setQueryData on mutation success not triggering the rerender of all consumers about query HOT 1 CLOSED

okay I went into this a bit, and it works if I just setQueryData to a newly created todo. I think the problem is that your todo-service returns the same object references, so our structuralSharing sees them as equal and optimizes the re-render away.

If I change it to:

completeTodo: async () => {
  await wait(100);

  const newTodo = { ...todo };

  newTodo.completed = true;
  newTodo.completedBy = "John Doe";

  return newTodo;
},

everything works. I don't think this is an issue that you would get with real API requests.

from query.