# `react-doctor/no-chain-state-updates`

Disallow chaining state changes in an effect.

- **Status:** Active
- **Category:** Bugs
- **Assessment:** Evidence-required risk
- **Required evidence:** source code
- **Default configuration:** Enabled
- **Default severity:** warn
- **Scope:** All supported frameworks
- **Active when:** React 19 projects
- **Disabled when:** react:18
- **Requirements:** react
- **Tags:** test-noise
- **Priority:** 44 (P3)
- **Source:** oxlint-plugin-react-doctor
- **Rule set:** oxlint-plugin-react-doctor 0.9.3 (prompt schema 2)
- **Documentation:** [Official documentation](https://react.dev/learn/you-might-not-need-an-effect#chains-of-computations)

## Validation prompt

Confirm the detector match and collect the required evidence before deciding whether an edit is warranted.

Fires on a cleanup-less `useEffect` or `useLayoutEffect` whose dependencies include state and which synchronously updates other state from unrelated data. It follows React imports, namespace calls, exact aliases, and semantic or isomorphic aliases that select between effect hooks. It excludes convergent previous/current snapshot guards, externally driven state, external-system synchronization, and state that must read committed Document Object Model (DOM) state. React 18 projects are excluded because this rule is disabled when the supported React range includes 18.

## Evidence boundary

The diagnostic proves only that the detector's modeled source pattern matched. It does not prove runtime impact, product intent, rendered failure, or that one remediation is correct.

Establish the environment, explicit repository policy, relevant exceptions, and required rendered or runtime evidence before deciding the occurrence. This page’s Assessment and Required evidence fields define the review contract.

Default severity is registry metadata. Use the occurrence's JSON severity after repository configuration when ordering real findings.

Record one outcome:

- **Confirmed failure:** The required evidence establishes the violation.
- **Rejected:** A documented exception or false-positive predicate applies.
- **Needs evidence:** Named evidence can still be collected.
- **Unavailable:** Required evidence cannot be collected in this run.
- **Waived with evidence:** An authorized, scoped exception applies to an established failure.
- **Observation:** The review records an optional tradeoff without claiming a defect.

A waiver records its scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

## Fix prompt

Apply this candidate correction only after the required evidence confirms the risk.

Compute both values in the event handler that updates the upstream state, then call both setters so React batches one render. Remove the second state variable when it always derives from the first, and compute it during render or with `useMemo`. See https://react.dev/learn/you-might-not-need-an-effect#chains-of-computations

## Repository-wide copy prompt

Use this only for a repository-wide pass after validating each occurrence. For one occurrence, use the occurrence-level guidance above.

````text
Fix every confirmed `react-doctor/no-chain-state-updates` diagnostic in the current repository.

Required change:
- Compute both values in the event handler that updates the upstream state, then call both setters so React batches one render. Remove the second state variable when it always derives from the first, and compute it during render or with `useMemo`. See https://react.dev/learn/you-might-not-need-an-effect#chains-of-computations.

Validation before editing:
Fires on a cleanup-less `useEffect` or `useLayoutEffect` whose dependencies include state and which synchronously updates other state from unrelated data. It follows React imports, namespace calls, exact aliases, and semantic or isomorphic aliases that select between effect hooks. It excludes convergent previous/current snapshot guards, externally driven state, external-system synchronization, and state that must read committed Document Object Model (DOM) state. React 18 projects are excluded because this rule is disabled when the supported React range includes 18.

Constraints:
- Make the smallest change that fixes the root cause.
- Preserve behavior and interfaces unrelated to this diagnostic.
- Reuse existing project components, utilities, and conventions.
- Do not introduce render-phase side effects, render-phase state updates, or Hooks rule violations.
- Adapt identifiers and framework details instead of copying blindly.
- Do not disable the rule or suppress matching code.
- Confirm this rule is enabled for the project: `React 19 projects`.
- Do not edit code when this condition applies: react:18.

Assessment:
- Record detector evidence, applicability facts, assumptions, missing evidence, and the rule class for this occurrence.
- Return one outcome: Confirmed failure, Rejected, Needs evidence, Unavailable, Waived with evidence, or Observation.
- A waiver records the established failure, scope, authority, evidence, and review or expiry condition. It is not a pass or false positive.

Verification:
- Run focused tests for the changed behavior.
- Run React Doctor and confirm this diagnostic no longer appears from changed code.
- Run an unfiltered scan of the affected scope before claiming no cross-category regression.
- Report the files changed and any checks you could not run.
````