feat(linter/eslint): add no_unreachable rule.

[rzvxa]

no-unreachable

Status: This one might take a while, Have to resolve some issues with the control flow graph to eliminate false positives, and as of today I couldn't figure out a good solution to resolve all of the shortcomings of our current implementation. This one is an important rule - some might even say essential - and the cfg changes can help with the future development of rules and/or transformers relying on this data; So please bear with me.

[graphite-app]

Your org has enabled the Graphite merge queue for merging into main

Add the label “merge” to the PR and Graphite will automatically add it to the merge queue when it’s ready to merge. Or use the label “hotfix” to add to the merge queue as a hot fix.

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

[rzvxa]

• feat(linter/eslint): add no_unreachable rule. #3238 👈
• main

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

Join @rzvxa and the rest of your teammates on Graphite

[codspeed-hq]

CodSpeed Performance Report

Merging #3238 will degrade performances by 31.08%

_{Comparing 05-11-feat_linter_eslint_add_no_unreachable_rule (4b0951e) with main (fdb31c3)}

Summary

❌ 2 regressions
✅ 25 untouched benchmarks

⚠️ Please fix the performance issues or acknowledge them on CodSpeed.

Benchmarks breakdown

	Benchmark	main	05-11-feat_linter_eslint_add_no_unreachable_rule	Change
❌	linter[cal.com.tsx]	3.1 s	4.2 s	-25.87%
❌	linter[checker.ts]	5.9 s	8.5 s	-31.08%