[Enhancement]: jsx-handler-names reports error with inline ternary conditional callbacks

Description

<MyComponent
  onClick={isClickDisabled ? undefined : handleClick}
/>

ESLint: Handler function for onClickNext prop key must be a camelCase name beginning with 'handle' only(react/ jsx-handler-names)

Contributor guide

Tech stack

javascriptreact

Domain

frontendtooling

Issue type

feature

DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.

3

Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.

1-3 hours

Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.

fresh

ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.

clear

Prerequisites

JavaScriptESLint plugin developmentReact event handlers

Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.

65

Research direction

Examine the implementation of the `jsx handler names` rule in `lib/rules/jsx handler names.js`. Look for where the prop value is checked for a handler pattern. The rule currently fails on ternary expressions; research how to properly evaluate ternary nodes (ConditionalExpression) to check if both branches are valid handlers or if one is undefined/valid. Check how other rules handle similar patterns, e.g., `jsx no target blank`. After understanding, propose a fix that allows the ternary expression if it returns a properly named handler or undefined.