react-doctor/no-set-state

Lift state up or use an external store instead of this.setState.

Validation prompt

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

Fires on a this.setState(...) call expression whose callee is exactly this.setState and that sits inside a recognized React component: an es5 createReactClass({...}) or an es6 class extends React.Component. It does NOT fire on this.setState used in a plain function that isn't a component, nor on merely referencing the method without invoking it (e.g. this.someHandler = this.setState).

Suppress when: a legitimate class component kept on purpose: error boundaries, third-party/legacy integrations, or code not yet migrated: where local class state is still the correct tool; this is a style/architecture rule, so confirm the codebase has actually committed to banning class state before flagging.

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, repository policy, exceptions, and required rendered or runtime evidence before deciding the occurrence.

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 condition. It is not a pass or false positive.

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

Fix prompt

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

Move the state out of the class: lift it to a parent and pass it down as props, or back it with an external store (Redux/Zustand/Flux) and dispatch instead of calling this.setState({count}). Where the component itself should own the state, convert it to a function component and use a hook: const [count, setCount] = useState(0). If this class component must stay (e.g. an error boundary), suppress the finding on that line with a written justification. See https://oxc.rs/docs/guide/usage/linter/rules/react/no-set-state

Repository-wide copy prompt

Use this repository-wide prompt only after validating each occurrence. For one occurrence, use the guidance above.