feat(utils): add ESLint CodePath selector types

[Zamiell]

PR Checklist

• Addresses an existing open issue: fixes Enhancement: Support CodePath rule listener methods #6993
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Adds exported CodePath interfaces and un-commented the onCodePathStart and onCodePathEnd methods, which makes things slightly less painful for people who have custom rules that use this feature.

Based on: #6679

[typescript-eslint]

Thanks for the PR, @Zamiell!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	0b1de44
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65523587cb214c00088c1bd0
😎 Deploy Preview	https://deploy-preview-7551--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (no change from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit aa3f504. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

🟥 Failed Commands
nx run-many --target=lint --parallel

✅ Successfully ran 19 targets

• nx test eslint-plugin --coverage=false
• nx test scope-manager --coverage=false
• nx run types:build
• nx test utils --coverage=false
• nx test rule-schema-to-typescript-types --coverage=false
• nx test visitor-keys --coverage=false
• nx test type-utils --coverage=false
• nx run repo-tools:postinstall-script
• nx test repo-tools --coverage=false
• nx test typescript-estree --coverage=false
• nx test parser --coverage=false
• nx test eslint-plugin-internal --coverage=false
• nx test eslint-plugin-tslint --coverage=false
• nx test ast-spec --coverage=false
• nx build website
• nx run-many --target=typecheck --parallel
• nx run integration-tests:test
• nx run eslint-plugin:generate:configs
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint

---

Sent with 💌 from NxCloud.

[Zamiell]

CI is drunk, the codebase builds just fine for me locally (after my latest commit). Can a maintainer reset the CI cache or something?

[Zamiell]

Oh, actually on second thought, it just looks like it is failing a spell check on code that is unrelated to my PR, so a maintainer should fix that.

[bradzacher]

looking good so far!

[Zamiell]

ok, i addressed the feedback and merged with the main branch

[bradzacher]

For future reference - I'd avoid working from a repo in an org account and instead work from a fork on your personal account. We maintainers can't modify your PR at all - even the standard "update branch" button which auto-merges main doesn't work. This can make it difficult to manage your OSS contributions because we have to ping you and wait for your action even for trivial things like merging main - which we sometimes need to do if main was broken (eg in this case the CI was broken!).

Please merge main so we can kick off the CI again with the latest deps then we can merge this.

[Zamiell]

Please merge main

done!

[JoshuaKGoldberg]

...aaaand lint is broken on main. Sorry 😄 we can just take this as-is and fix linting separately. #7913