Thanks for the PR, @JoshuaKGoldberg!

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.

☁️ Nx Cloud Report

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

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	8b8b644
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/63f635727657ce0008facc0a
😎 Deploy Preview	https://deploy-preview-6510--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.

I feel weird mentioning semicolons as just formatting, because they can affect runtime behavior. 😅 The decision between using them only where needed and always, is stylistic. Of course this is nit and it may be clear for everyone what is meant here.

I feel weird mentioning semicolons as just formatting, because they can affect runtime behavior.

It doesn't change runtime behavior; it changes how the code parses altogether. I guess when we say "change semicolons" it's really implied that we are changing it in a syntactically insignificant way.