test(linter/no-fallthrough): add another test case with logical expr

[camc314]

fixes #14828

[camc314]

• test(linter/no-fallthrough): add another test case with logical expr #14832 👈 (View in Graphite)
• 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 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.

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

[Copilot]

Pull Request Overview

This PR adds a test case to the no_fallthrough linter rule to verify correct handling of switch statements with logical expressions in JSX contexts. The test addresses issue #14828.

• Adds a single passing test case that validates fallthrough detection works correctly when switch cases contain logical operators (&&) within a JSX map callback

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[graphite-app]

Merge activity

• Oct 20, 9:45 PM UTC: camc314 added this pull request to the Graphite merge queue.
• Oct 20, 9:50 PM UTC: Merged by the Graphite merge queue.

[codspeed-hq]

CodSpeed Performance Report

Merging #14832 will not alter performance

_{Comparing c/10-20-test_linter_no-fallthrough_add_another_test_case_with_logical_expr (a64180e) with main (b8f8ce5)¹}

Summary

✅ 4 untouched
⏩ 33 skipped²

Footnotes

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

2. 33 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. ↩