Example of how to restore offline changes

Struggling with how to restore offline changes so that they reflect on the UI.

The following offline mutation saves the data to the offline store and reflects immediately on the UI - however when I refresh the page the changes are no longer reflected.

const [ updateTodo ] = useOfflineMutation(gql`
  mutation UpdateTodo ($id: ID! $name: String!)
    updateTodo (id: $id name: $id) {
      id
      name
    }
  }
`)

await updateTodo({
  variables: { id: item.id, name: item.name },
  returnType: 'Todo',
  operationType: CacheOperation.REFRESH,
  idField: 'id'
})

I’ve read through the docs and came across mutationCacheUpdates which looks as if it’s designed to do the trick but I can’t work out for the life of me how to use it - any pointers/examples would be much appreciated - cheers!

[wtrocki]

Most of the queries from client are not named to reduce payload size. Named query/mutation can contain multiple underlying graphql queries and mutations. That is the reason we require actual query name in global cache updates. In terms of our underlying engine each operation is processed separately by conflict/offline engine anyway.

I guess we need to document good patterns to not name your queries if single operation is send etc. Also once we integrate offix with graphback we can enforce some standards or even generate cache update functions as they would be easy to build - then our helpers could be deprecated

[darahayes]

Have you tried the following?

const mutationCacheUpdates = {
  sendMessage: sendMessageUpdateFn
}