feat(linter): add react/jsx-handler-names rule

[takuji]

This PR adds the react/jsx-handler-names rule.

Dropped test cases

Test cases where the bind-this operator :: is used are dropped because the current oxc parser doesn't seem to understand it.
For example, if you test the following code:

<TestComponent onChange={props::handleChange} />

You'll get an output like this:

-------- source --------

<TestComponent onChange={props::handleChange} />

-------- error --------

  × Expected `}` but found `:`
   ╭─[jsx_handler_names.tsx:1:31]
 1 │ <TestComponent onChange={props::handleChange} />
   ·                               ┬
   ·                               ╰── `}` expected
   ╰────

All the dropped test cases are in this commit: d80dcfa

works towards #1022

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[codspeed-hq]

CodSpeed Instrumentation Performance Report

Merging #13079 will not alter performance

_{Comparing takuji:jsx-handler-names (82fd8df) with main (b2d59a2)}

Summary

✅ 34 untouched benchmarks

[camc314]

Test cases where the bind-this operator is used are dropped because the current oxc parser doesn't seem to understand it.

mind expanding on this with an example of what the parser is failing to parse

[takuji]

@camc314 I've added details in the PR description.

[camc314]

@camc314 I've added details in the PR description.

thanks, not sure why the library has test cases like that, the proposal hasn't been updated in 8 yrs and was never shipped

[Copilot]

Pull Request Overview

This PR implements the react/jsx-handler-names rule to enforce consistent naming conventions for JSX event handlers and their corresponding props. The rule ensures handler functions start with specified prefixes (default "handle") and prop names start with specified prefixes (default "on").

• Adds complete implementation of the jsx-handler-names rule with configurable options
• Includes comprehensive test coverage for various scenarios and edge cases
• Handles component name ignore patterns using glob matching

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 6 comments.

File	Description
crates/oxc_linter/src/rules/react/jsx_handler_names.rs	Complete rule implementation with configuration parsing, regex compilation, and handler/prop validation logic
crates/oxc_linter/src/rules.rs	Rule registration in the linter module system
crates/oxc_linter/src/snapshots/react_jsx_handler_names.snap	Test output snapshots showing expected diagnostic messages

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.
You can also share your feedback on Copilot code review for a chance to win a $100 gift card. Take the survey.}

[camc314]

thank you