ESlint: eslint-plugin-react-hooks is going too far

[zettadam]

I think that eslint-plugin-react-hooks rules might be going to far. I have a function that starts with use prefix but it doesn't mean that I wrote a React hook, especially when the code in question is in not related or used with React. Here's what I mean:

[gaearon]

Sure but that’s kind of how the plugin works. I suggest excluding this file/folder from the plugin since it doesn’t have React-related code in it.

[zettadam]

Wait a minute! You're saying that any function that starts with use prefix is a hook now?

[gaearon]

From the plugin’s perspective, yes. (In the absence of an effect tracking type system or special syntax that’s the best we can do.)

[zettadam]

I understand the perspective, though I wasn't expecting it. Perhaps this case could be documented somewhere with a short note. I wouldn't know it if I hadn't seen it. It struck me as quite a grab of vocabulary since use is such a common word to start a function name with.

[gaearon]

Yeah we needed to balance something that’s short enough to look natural and that’s relatively unclaimed. While not entirely uncommon, we’ve found “use” way less common for function names (it’s typically used for booleans) than other short prefixes.