☁️ Nx Cloud Report

CI is running/has finished running commands for commit 72527e5. 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

Sent with 💌 from NxCloud.

Thanks for the PR, @bradzacher!

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. As a thank you, your profile/company logo will be added to our main README which receives thousands of unique visitors per day.

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	72527e5
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/63f3e5e66415b00008a2a581
😎 Deploy Preview	https://deploy-preview-5573--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

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

The actions are all setup and working just fine, but there is two problems to solve.

1. Parsing new features in old versions.
   • Old TS parsers will crash on new syntax which will fail our snapshot tests in the scope analyser and parser, and will fail ESLint rule tests.
2. Extension rules behave differently on old ESLint versions.
   • Some of our extension rules are built directly on top of the core rule's code - this means that their behaviour is dependent on the core rule's behaviour, which means the tests (which are written against the latest version) can break.

We need a way to:

1. specify a minimum required TS version for a given snapshot.
2. specify a minimum required TS version for a given ESLint rule test.
3. specify a minimum required ESLint version for a given ESLint rule test.

Lots of merge conflicts and this is taking up space in the PR queue. I'm going to close this old draft just to keep the queue small.