react-doctor/jsx-handler-names

Use the `on…` prefix for event-handler props and `handle…` for the functions that handle them.

Validation prompt

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

Fires on a JSX attribute whose value is a member-expression or this.props chain (and, when opted in via checkLocalVariables/checkInlineFunction, a bare identifier or single-call arrow) where the prop name and handler name disagree on prefix: an on…-prefixed prop wired to a value that does NOT start with handle… (e.g. onChange={this.onChange} or onChange={this.doSomethingOnChange}), or a non-on… prop wired to a handle…-prefixed value (e.g. handleChange={this.handleChange}). ref, empty expressions, and plain literals are skipped by default (literals fire only when checkLocalVariables is enabled).

Suppress when: conditional-render APIs that reuse the on namespace for non-event data, such as solid-js <Show when={props.onFoo}>, where the prop when carries the on-named value props.onFoo, which is not an event handler.

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.

Align the two names: give event-handler props the on prefix and name the function they receive with handle (e.g. <Button onClick={handleClick} />, not onClick={clickButton} or whenClick={handleClick}). When a prop's value legitimately reuses the on namespace for non-handler data: as in solid-js <Show when={props.onFoo}>, where props.onFoo is conditional-render data, not an event handler: disable the rule on that line or add the component to ignoreComponentNames rather than renaming. See https://oxc.rs/docs/guide/usage/linter/rules/react/jsx-handler-names

Repository-wide copy prompt

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