T
TanStack•2mo ago
adverse-sapphire

No mutationFn found (offline)

// Responsible for resuming paused mutations
export const SyncPausedMutations = () => {
  const queryClient = useQueryClient();
  const createIssueMutationOptions = useCreateIssueMutationOptions();

  useEffect(() => {
    queryClient.setMutationDefaults(
      createIssueMutationOptions.mutationKey!, 
      createIssueMutationOptions
    );
  }, [queryClient, createIssueMutationOptions]);

  useEffect(() => {
    queryClient
      .resumePausedMutations()
      .then(() => queryClient.invalidateQueries())
      .catch((e) => {
        console.log('Failed to resume mutations', e);
      });
  }, []);

  return null;
};
// Responsible for resuming paused mutations
export const SyncPausedMutations = () => {
  const queryClient = useQueryClient();
  const createIssueMutationOptions = useCreateIssueMutationOptions();

  useEffect(() => {
    queryClient.setMutationDefaults(
      createIssueMutationOptions.mutationKey!, 
      createIssueMutationOptions
    );
  }, [queryClient, createIssueMutationOptions]);

  useEffect(() => {
    queryClient
      .resumePausedMutations()
      .then(() => queryClient.invalidateQueries())
      .catch((e) => {
        console.log('Failed to resume mutations', e);
      });
  }, []);

  return null;
};
I am using this component to be responsible for registering and resuming the paused mutation in the authenticated root page because the mutation depends on some contexts related to the session. But, by having this, I get the famous "No mutationFn found". Why does this happen? I debugged the code, and I can guarantee that setMutationDefaults runs before executing the resume.
0 Replies
No replies yetBe the first to reply to this messageJoin

Did you find this page helpful?