react-doctor/jsx-no-new-function-as-prop

Memoize the callback (useCallback) or hoist it outside the component to keep a stable reference across renders.

Validation prompt

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

Fires when a JSX prop on a custom component receives a freshly-allocated function each render: an inline arrow/function expression, new Function/Function(), a .bind() call, a logical/ternary that produces one, or a render-local identifier bound to such: but ONLY when same-file analysis PROVES the consumer is wrapped in React.memo/memo/forwardRef/observer. Intrinsic HTML elements, one-shot lifecycle/render-prop names (onMount, fallback, render*, *Renderer), parameter-binding wrappers like (e) => fn(arg, e), hook-returned handlers (const h = useFoo()), and test files are all skipped by design.

Suppress when: a wrapper the rule misclassified as fixable when it actually closes over unstable outer values: useCallback can't stabilize it, so the only "fix" would be a data-flow refactor with no measurable gain unless the consumer is truly memoised. Also note the whole rule is disabled under react-compiler, which auto-memoizes inline callbacks.

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.

Give the prop a stable reference: wrap the handler in useCallback(fn, [deps]), or hoist a closure-free function above the component (const handleClick = () => {...} at module scope). When the wrapper must capture per-render args (onClick={(e) => fn(id, e)}), pass the data down instead (<Child id={id} onClick={fn} />) rather than forcing a callback. Only worth doing because the consumer here is memoised, so a fresh reference defeats its memo bailout. See https://oxc.rs/docs/guide/usage/linter/rules/react_perf/jsx-no-new-function-as-prop

Repository-wide copy prompt

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