react-doctor/no-prop-types

Move propTypes to TypeScript types: `type Props = { value: number }; function Component(props: Props)`: React 19 ignores runtime propTypes

Validation prompt

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

Fires on two idioms whose receiver is a Capitalized identifier/class name: (1) an AssignmentExpression with operator '=' whose left is a MemberExpression with a 'propTypes' property (Identifier key, or computed Literal 'propTypes') on an Identifier object that passes the uppercase-name test, e.g. Component.propTypes = { value: PropTypes.number }; and (2) a static PropertyDefinition keyed 'propTypes' inside a ClassBody whose class (ClassDeclaration/ClassExpression id, or the VariableDeclarator id binding a ClassExpression) is uppercase-named, e.g. class Component { static propTypes = {...} }. The uppercase-receiver heuristic deliberately excludes lowercase objects, so config.propTypes = {...} or options.propTypes is never flagged: suppress those as well as any non-component object that happens to expose a propTypes field. The rule is version-gated upstream in the oxlint plugin source (requires react:19), so a flagged finding is already on a React 19+ project; still suppress if you can establish the code is genuinely pre-React-19, where propTypes still runs.

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.

Delete the propTypes object (and the prop-types import) and describe the contract with a TypeScript prop type instead: type ComponentProps = { value: number; onChange: (v: number) => void }, then annotate the component as function Component(props: ComponentProps) or class Component extends React.Component<ComponentProps>. propTypes also validated values at runtime: React 19 no longer does: so for props carrying genuinely untrusted external data, add an explicit runtime check or schema parse (e.g. zod) in the component body rather than relying on the removed propTypes mechanism. See https://react.dev/blog/2024/12/05/react-19#removed-proptypes-and-defaultprops

Repository-wide copy prompt

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