react-doctor/no-react19-deprecated-apis

Review React 19 ref-as-prop migrations; keep useContext unless a conditional context read specifically benefits from use(Context)

Validation prompt

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

Fires when forwardRef or useContext are imported from react on a detected React 19+ project. Both still work. A top-level useContext call gains no correctness benefit from mechanical replacement; use(Context) is useful when a context read must be conditional or inside a loop. Removing forwardRef is an app-level migration decision and may break React 18 consumers or a library's published component and type surface.

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.

Keep useContext for ordinary top-level reads; use use(Context) only where React 19 conditional or loop-based reading is actually needed. In a React-19-only application, a function component may accept ref as a prop after callers, TypeScript types, and tests are updated. Libraries supporting React 18 should retain forwardRef until their compatibility range and public types deliberately change. See https://react.dev/blog/2024/12/05/react-19#ref-as-a-prop

Repository-wide copy prompt

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