Bug: eslint-plugin-react-hooks `exhaustive-deps` rule shouldn't warn when using an object's property about react

[billyjanitsch]

This is by design. fetcher.submit(...) passes fetcher to the method call as this, so the rule is correct to require fetcher as a dependency. You can destructure to get a function that can be used as a dependency:

const fetcher = useFetcher();
const {submit} = fetcher
const onClick = useCallback(() => submit(XXX), [submit]);

See #16265, as well as #20755 for a proposal to make this configurable.

[julianhille]

whoever reaches here:
do not use fetcher as a dependecy the fetcher object is not stable and if you do something like

const fetcher = useFetcher();

useEffect(() => {...}, [fetcher])

that will cause the useEffect to be called everytime as fetcher changes everytime.

[julienw]

Ah interesting ! Yes I see the point.
Indeed I didn't want to do what you suggest because I wasn't sure if a proper this was needed... but failed to make the connection 😂

I'm closing the issue then. Hopefully this could help other folks though.