[eslint-plugin-react-hooks] "Rules of hooks" considers any function beginning with "use" to be a React Hook

Do you want to request a feature or report a bug?

This seems like a bug.

What is the current behavior?

1. Follow the steps for adding the linting rules outlined on the Rules of Hooks page.
2. Create a plain JS function with a name that begins with use, e.g. useFoo. Call this function from within another plain JS function, e.g. testFoo.

   function useFoo() {
   }
   
   function testFoo() {
     useFoo();
   }
   

3. The linter will complain:

   React Hook "useFoo" is called in function "testFoo" which is neither a React function component or a custom React Hook function  react-hooks/rules-of-hooks
   

What is the expected behavior?

Ideally, the rule would ignore functions that begin with use but are not React Hooks.

[micha149]

@gaearon whats up with other functions beginning with use? For example ramdas useWith… Maybe the rule should check if any of the problematic functions like useState, useEffect etc. is used inside my hook, otherwise the checks can be handled differently.

Otherwise something like a whitelist of functions which are not hooks might be useful as a configuration parameter.

[cjcenizal]

@jtiscione I understand you’re upset and this rule is causing problems for you. At the same time, remember you’re using open-source software. You’re not paying for it and the maintainers of this tool don’t owe you anything. You’ll get farther along if you give yourself time to cool down before posting a complaint about OSS.

When you do post a complaint, you’ll maximize your chances of getting what you want by avoiding incendiary language like “absolutely unacceptable”, “screaming”, “atrocious”, “carelessly”, and “doesn’t understand”. I’ve found that it helps to clearly describe the problem I’m encountering and propose some solutions or ask questions to understand the problem space better.

How you communicate establishes your own reputation, for better or worse!