Recommend eslint:no-label for functional setState

[tsiq-swyx]

this is a pretty common mistake when using the functional form of setState:

and we have no warning in React (yet) for this when it happens. easiest guard is having eslint:no-label tell you about it. Should we add a mention in the setState docs?

[alexkrolick]

Maybe add a note here? https://reactjs.org/docs/faq-state.html#what-is-the-difference-between-passing-an-object-or-a-function-in-setstate

[tsiq-swyx]

yeah. i'm also trying to add a warning in react itself: facebook/react#13111

[rickhanlonii]

On the new site I'm not sure it makes sense to recommend the lint rule, especially in 2025 where types and strict mode should catch this, but it would probably be good to have a Pitfall callout or Troubleshooting item here: https://react.dev/reference/react/useState#troubleshooting