react-doctor/no-initialize-state

Disallow initializing state in an effect.

Validation prompt

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

Fires on a useEffect with no non-setter deps (so it runs once on mount, or only after setState calls) that synchronously calls setState: the classic componentDidMount 'load initial value into state' pattern.

Suppress when: SSR hydration where the value must differ between server and client (window-only APIs), but that has a dedicated fix via useSyncExternalStore rather than an effect.

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 a pure initializer into useState's lazy form: useState(() => computeInitial()), which avoids evaluating it on ordinary re-renders. React may invoke the initializer twice in development Strict Mode, so it must be pure and safe to repeat. For browser-only sources in an SSR application, do not read window or localStorage in the initializer; use useSyncExternalStore with a matching getServerSnapshot, or serialize an initial value from the server. See https://react.dev/reference/react/useState#avoiding-recreating-the-initial-state

Repository-wide copy prompt

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