feat(linter): implement eslint/camelcase rule

[tt-a1i]

Summary

Implements the ESLint camelcase rule that enforces camelCase naming conventions for identifiers.

Features:

• Checks variable declarations, function names, parameters, object properties, class members, imports, exports, and destructuring patterns
• Supports properties: "always" | "never" option to control property name checking
• Supports ignoreDestructuring: true option to skip destructuring identifiers
• Supports ignoreImports: true option to skip import identifiers
• Supports allow option with literal strings or regex patterns (patterns starting with ^ or ending with $ are treated as regex)
• Allows leading/trailing underscores (_private, trailing_)
• Allows ALL_CAPS constant style (CONSTANT_VALUE)

Implementation notes:

• Pre-compiles regex patterns in from_configuration for better performance
• Handles both destructuring declarations (const { foo_bar } = obj) and destructuring assignments (({ foo_bar } = obj))

Closes #5535

[codspeed-hq]

CodSpeed Performance Report

Merging #16908 will not alter performance

_{Comparing tt-a1i:feat/eslint-camelcase (fb2d605) with main (8c9cafe)¹}

Summary

✅ 4 untouched
⏩ 41 skipped²

Footnotes

1. No successful run was found on main (c16082c) during the generation of this report, so 8c9cafe was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 41 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[camc314]

I re-ported the test cases and they're failing.

It looks like you missed a lot of test cases when porting this rule originally.

[tt-a1i]

I re-ported the test cases and they're failing.

It looks like you missed a lot of test cases when porting this rule originally.

Thanks for re-porting these — you’re right, my initial port missed a bunch of ESLint coverage
and I was drifting by patching via extra AST handlers.

I’ve reworked the rule to follow ESLint’s approach more closely using semantic analysis in
run_once (declared symbols + resolved references + unresolved/through refs), and updated the
snapshots based on a full re-port. While doing that I also fixed a few semantic gaps:

• ignoreGlobals: now only skips explicitly configured globals (and env globals), undefined/
  implicit globals still report
• ignoreDestructuring: added ({ foo: foo } = obj) equals-to-original handling
• AssignmentPattern: only skips the right side identifier (ESLint backward-compat behavior)
• ExportSpecifier: checks the exported name (not local)

The rewrite is in 07ef1b6 (plus 1c38fec to resolve conflicts). Could you take another look /

[tt-a1i]

hey @camc314, just checking if you had a chance to look at the rewrite? no rush, happy holidays!

[bradzacher]

Based on the PR description and code comments I presume this was - at least in large part - generated using AI tooling.

Please ensure that the PR description is updated to note the AI usage in accordance with our policy, preferably including models/tools used and a confirmation that you have personally reviewed the code generated and ensured it works/makes sense: https://oxc.rs/docs/contribute/introduction.html#ai-usage-policy.

---

That aside, we've discussed internally and we'd instead be looking to implement @typescript-eslint/naming-convention instead of camelcase given that naming-convention is allows you to do camelcase and much, much more.

[tt-a1i]

Based on the PR description and code comments I presume this was - at least in large part - generated using AI tooling.

Please ensure that the PR description is updated to note the AI usage in accordance with our policy, preferably including models/tools used and a confirmation that you have personally reviewed the code generated and ensured it works/makes sense: https://oxc.rs/docs/contribute/introduction.html#ai-usage-policy.

That aside, we've discussed internally and we'd instead be looking to implement @typescript-eslint/naming-convention instead of camelcase given that naming-convention is allows you to do camelcase and much, much more.

makes sense, naming-convention is more comprehensive anyway.
and yeah my bad on the AI disclosure — been adding it to my other PRs