Prevent mutation from caching

I have an editable element. On every change I send the serialized content to my server using a mutation, so one mutation per change.

Now cache entries in ROOT_MUTATION pile up. The serialized string can be quite long. Is there any way to prevent a mutation from caching the result?

I use version ^3.0.0-beta.23.

[cloudratha]

I had the same issue, and kinda thought it would be a configuration in the cache to mark a mutation as not cacheable. But it’s on the mutation level.

const result = useMutation(SOME_MUTATION, {
    fetchPolicy: 'no-cache',
});

no-cache does not read or write to the cache.

The docs for useMutation don’t show the fetchPolicy but it’s there.

[cloudratha]

@henryqdineen you can use the onComplete handler and use the client to write to the cache.

export default function Login() {
  const client: ApolloClient<any> = useApolloClient();
  const [login, { loading, error }] = useMutation<LoginTypes.login, LoginTypes.loginVariables>(
    LOGIN_USER,
    {
      onCompleted({ login }) {
        client.writeQuery({
          query: gql`
             query GetIsLoggedIn {
                isLoggedIn
             }
          `,
          data: {
            isLoggedIn: true
          }
        });
        // client.writeData({ data: { isLoggedIn: true } });
      }
    }
  );

  if (loading) return <Loading />;
  if (error) return <p>An error occurred</p>;

  return <LoginForm login={login} />;
}

Taken from the docs: https://www.apollographql.com/docs/tutorial/mutations/#expose-apollo-client-with-useapolloclient But I hastily updated the example to use the writeQuery, as writeData is deprecated and removed in v3.