[New] hook-use-state: add option to use useState hook with no value

[azat-io]

This is useful if you want to forcibly re-render a component

[codecov]

Codecov Report

Merging #3577 (01b8f81) into master (13f5c19) will increase coverage by 0.00%.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##           master    #3577   +/-   ##
=======================================
  Coverage   97.62%   97.62%           
=======================================
  Files         132      132           
  Lines        9295     9298    +3     
  Branches     3400     3402    +2     
=======================================
+ Hits         9074     9077    +3     
  Misses        221      221           

Impacted Files	Coverage Δ
lib/rules/hook-use-state.js	100.00% <100.00%> (ø)

[ljharb]

This seems like a special enough case that it warrants an eslint override comment, and not a whole new option to the rule. What codebases would have more than one occurrence of this pattern?

[azat-io]

I would suggest disabling error messages if no value is specified.

It doesn't sound like a naming problem:

const [, forceUpdate] = useState({})

[ljharb]

This feels like an antipattern - components should never need to rerender unless props or state have changed.

[ljharb]

Closing pending further discussion, since I'm not yet convinced this isn't an antipattern. I'd be happy to reopen if there's a reasonable use case where this option would be helpful.