Updating the Cache After Mutations
A successful mutation does not automatically mean that every affected cached query is correct. The client may need to update or invalidate cached data.
For example, creating a new task may require inserting the task into a cached task list. Deleting a task may require removing it from cached lists. Updating a user may require updating the normalized user entity.
Good GraphQL client design considers the relationship between every mutation and the queries whose results it changes.