react-doctor/prefer-function-component

Re-write the class component as a function component using hooks.

Validation prompt

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

Fires on any ClassDeclaration or ClassExpression that extends Component, PureComponent, React.Component, or React.PureComponent: i.e. an ES6 React class component that could be a function with hooks. By default, error-boundary classes (those defining componentDidCatch or getDerivedStateFromError) are exempt, but setting allowErrorBoundary:false makes them fire too.

Suppress when: when allowJsxUtilityClass:true is configured the rule also flags non-Component classes that merely contain JSX, which may be legitimate render-helper utilities rather than components needing conversion.

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.

Convert only after mapping behavior rather than translating lifecycle names mechanically. Derive render data directly, move event-owned work to handlers, and use Effects only for external synchronization with dependencies and cleanup that preserve mount/update/unmount timing. Preserve getSnapshotBeforeUpdate semantics explicitly, and keep a class error boundary because hooks have no equivalent. Add focused tests for lifecycle ordering, refs, subscriptions, and error handling before and after the migration. See https://oxc.rs/docs/guide/usage/linter/rules/react/prefer-function-component

Repository-wide copy prompt

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