Is there a conflict with the other eslint-react/eslint-plugin plugin?

[binarykitchen]

In my project I'm using both plugins:

• "eslint-plugin-react-you-might-not-need-an-effect": "0.5.5" and
• "@eslint-react/eslint-plugin": "1.53.1",

It seems they overlap and have similar checks. I wonder if both are compatible with each other, or whether I should only pick one?

[NickvanDyke]

Could you elaborate? I only see overlap with https://www.eslint-react.xyz/docs/rules/hooks-extra-no-direct-set-state-in-use-effect which 1. ignores props and refs, and 2. does not provide any insight into the specific anti-pattern.

Similar story for the new eslint-plugin-react-hooks/set-state-in-effect, afaik.

See Rel1cx/eslint-react#1114 (comment) as well 🙂

[binarykitchen]

Thanks, mate. I think that thread Rel1cx/eslint-react#1114 (comment) says it all.
Looks like there is some overlap and needs further discussions.

I do really like your idea and thoughts, especially about those false positives you mentioned.

It's just that I'm running a productive site with hundred of users every day. That's why I will stick to v0.2.0 until this is sorted.

Don't make compromises when it comes to standards ;)

[NickvanDyke]

That's fair! If you do use this plugin again and experience any false positives/negatives, feel free to open an issue 😃