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 onhttps://opencollective.com/typescript-eslint.

✅ Deploy Preview fortypescript-eslint ready!

Name	Link
🔨 Latest commit	cdf7d90
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/64967b3da23c7f00070b8a6a
😎 Deploy Preview	https://deploy-preview-7033--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 yourNetlify site settings.

☁️ Nx Cloud Report

CI is running/has finished running commands for commitcdf7d90. 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 💌 fromNxCloud.

Can we also settle on a file naming convention? We seem to be using more kebab-casing (and some SCREAM_CASING) in the past.

The convention in/docs at least seems to be 95%Title_Snake_Case - which is what I used for new files and renamed existing files to. There are a fewUPPER_SNAKE_CASE but they're dying out.

I have no preference one way or the other though. (If it were up to me I'd usecamelCase orPascalCase heh)

Build error

3:04:51 PM: [ERROR] Unable to build website for locale en.3:04:51 PM: [ERROR] Error: Docusaurus found broken links!3:04:51 PM: 3:04:51 PM: Please check the pages of your site in the list below, and make sure you don't reference any path that does not exist.Note: it's possible to ignore broken links with the 'onBrokenLinks' Docusaurus configuration, and let the build pass.3:04:51 PM: Exhaustive list of all broken links found:3:04:51 PM: 3:04:51 PM: - On source page path = /packages/utils:3:04:51 PM:    -> linking to /custom-rules

Weirdly it didn't show up locally usingyarn start

@Josh-Cena there were a number of times that I moved files around and then ranyarn start and it wouldn't detect broken links (where we used relative file links to other mdx files). Is this expected withyarn start and it's only guaranteed to be detected with a proper build?

there were a number of times that I moved files around and then ranyarn start and it wouldn't detect broken links (where we used relative file links to other mdx files). Is this expected withyarn start and it's only guaranteed to be detected with a proper build?

Yes, the broken link detection only works reliably in build. Sometimes dev also reports link errors but I can't remember in which cases (usually when it blocks rendering the correct link)