[docs] Improve the error message of naming-convention/use-state

[bhollis]

Describe the bug

const [{ result, processing }, setState] = useState<ProcessState>({
  processing: false,
  resultStoreId: selectedStore.id,
  result: null,
});

This triggers "An useState call is not destructured into value + setter pair @eslint-react/naming-convention/use-state" but it shouldn't.

Reproduction

const [{ result, processing }, setState] = useState<ProcessState>({
  processing: false,
  resultStoreId: selectedStore.id,
  result: null,
});

Expected behavior

No error.

Platform and versions

Node v23.5.0
ESLint 9.19.0
@eslint-react/react-plugin 1.31.0

Stack trace

Additional context

No response

[bhollis]

I also get a warning for this code:

const [liveQueryLive, setLiveQuery] = useState(searchQuery ?? '');

[bhollis]

And this one:

const [options, setOptionsState] = useState<ItemPickerState>();

[Rel1cx]

The rule in the issue title should be use-state, not no-use-context.

[Rel1cx]

The main purpose of this rule is to enforce symmetric naming between state and setState. The code in the example above doesn't have a false positive, but the error message here has room for improvement. The current message might mislead users into thinking they're not using destructuring assignment.

[jonesmac]

I'm not sure if this is the same issue @Rel1cx but I have code that also gets flagged that seems like it might be similar. I have a custom hook called useAsyncEffect and this rule seems to flag it similarly.

useAsyncEffect(
    async () => {
...
    },
    [mod],
  )

gets flagged with warning An useState call is not destructured into value + setter pair. @eslint-react/naming-convention/use-state