Rule conflict between "useState call not destructured" vs. "variable declared but never used"?

SonarQube Cloud
1

With the following line of code …

const [broadcastSubscription, setBroadcastSubscription] = useState(null);

… if I only need to use the setter, then the unused broadcastSubscription variable triggers an “… is declared but its value is never read” error (typescript:S1854).

However, I can’t figure out how to correct this without creating new errors, because the “useState call is not destructured into a value + setter pair” error (typescript:S6754) is only satisfied if both variables share the same naming convention – prefixing with a _ (which turns off ESLint’s “variable not used” warning) isn’t allowed, nor is leaving the variable out entirely (e.g. [, setBroadcastSubscription] = …).

It’s as if these two rules are completely at odds with each other: One requires I define a variable I won’t be using, while the other complains if I don’t use my variables.

Is there any way around this, short of disabling these otherwise helpful rules?

Thank you kindly in advance for your help!

4

Hello @Eunomiac,

can you please provide more details about the use case for this? It’s not very common to have a state variable that you never read, so we would like to know what’s the exact use case that can justify an exception to the rule.

Cheers