fix(linter/hex-escape): false positive for String.raw

[camc314]

No description provided.

[camc314]

• fix(linter/hex-escape): false positive for String.raw #20497 👈 (View in Graphite)
• fix(linter/escape-case): false positive for String.raw #20496
• main

---

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 changes, fast-track this PR to the front of the merge queue

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.

This stack of pull requests is managed by Graphite. Learn more about stacking.

[Copilot]

Pull request overview

Fixes a false-positive in the unicorn/no-hex-escape lint rule by skipping hex-escape checks for template literals that are tagged with String.raw, where rewriting \x.. escapes would change runtime behavior.

Changes:

• Skip TemplateLiteral hex-escape linting when its parent is a String.raw tagged template expression.
• Simplify/adjust imports to match the updated logic.
• Add a new “pass” test case intended to cover String.raw behavior.

---

You can also share your feedback on Copilot code review. Take the survey.

[codspeed-hq]

Merging this PR will not alter performance

🎉 Hooray! codspeed-rust just leveled up to 3.0.5!

A heads-up, this is a breaking change and it might affect your current performance baseline a bit. But here's the exciting part - it's packed with new, cool features and promises improved result stability 🥳!
Curious about what's new? Visit our releases page to delve into all the awesome details about this new version.

✅ 4 untouched benchmarks
⏩ 52 skipped benchmarks¹

---

_{Comparing c/03-18-fix_linter_hex-escape_false_positive_for_string.raw_ (6ea617d) with main (50d59e9)²}

Footnotes

1. 52 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. ↩

2. No successful run was found on graphite-base/20497 (9911ab2) during the generation of this report, so main (50d59e9) was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

[camc314]

Merge activity

• Mar 18, 11:13 AM UTC: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.
• Mar 18, 11:16 AM UTC: camc314 added this pull request to the Graphite merge queue.
• Mar 18, 11:26 AM UTC: Merged by the Graphite merge queue.