eslint rule to prevent passing object returned by `useMutation` into hook dependency array?

I hit the issue that the object returned by

useMutation

useMutation

is not stable a few times (see also https://github.com/TanStack/query/issues/1858)
What do you think about adding an eslint rule that detects the following

 const mutate = useMutation(...);

 const handleClick = useCallback(() => {
    mutate();
  }, [mutate]); // <-- This should trigger the ESLint error

 const mutate = useMutation(...);

 const handleClick = useCallback(() => {
    mutate();
  }, [mutate]); // <-- This should trigger the ESLint error

GitHub

Issues · TanStack/query

Powerful asynchronous state management, server-state utilities and data fetching for the web. TS/JS, React Query, Solid Query, Svelte Query and Vue Query. - Issues · TanStack/query

TanStack•2y ago•

7 replies

still-lime

eslint rule to prevent passing object returned by `useMutation` into hook dependency array?

I hit the issue that the object returned by

useMutation

useMutation

is not stable a few times (see also https://github.com/TanStack/query/issues/1858)
What do you think about adding an eslint rule that detects the following

 const mutate = useMutation(...);

 const handleClick = useCallback(() => {
    mutate();
  }, [mutate]); // <-- This should trigger the ESLint error

 const mutate = useMutation(...);

 const handleClick = useCallback(() => {
    mutate();
  }, [mutate]); // <-- This should trigger the ESLint error

GitHub

Issues · TanStack/query

Powerful asynchronous state management, server-state utilities and data fetching for the web. TS/JS, React Query, Solid Query, Svelte Query and Vue Query. - Issues · TanStack/query

eslint rule to prevent passing object returned by `useMutation` into hook dependency array?

Similar Threads

eslint rule to prevent passing object returned by `useMutation` into hook dependency array?

Similar Threads

Similar Threads

Similar Threads