Exclude state setter from exhaustive-deps lint's dependencies check

There should be a way to exclude the setter returned by useRecoilState (or the value returned by useRecoilSetState) from the lint’s dependencies check since they are known stable values:

const setValue = useRecoilSetState(...);
// or const [value, setValue] = useRecoilState(...);

React.useEffect(() => {
  setValue(...)
}, []) // should not require setValue

It should work like the values returned by React.useState and React.useReducer, which I see currently is defined in the code of the lint:

https://github.com/facebook/react/blob/61dd00db24bec6305bd72908d3617b9f2a5183da/packages/eslint-plugin-react-hooks/src/ExhaustiveDeps.js#L296-L307

I’m not sure where to file this issue actually. Should I file an issue in the react-hooks lint repo and propose a way to add exception for dependencies?

[drarmstr]

thanks @drarmstr I didn’t think of that. So is that an expected use case or should we avoid it?

It’s a supported pattern and can be common. atoms or selectors are often passed in via props or part of some dynamic config. Or, a different atom may be used from an atomFamily() or selectorFamily() based on parameter values.

[thien-do]

Thanks! It should not be excluded then.