Thanks for the PR,@yeonjuan!

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	9af90d0
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65bc5ee9fd4f6400088df997
😎 Deploy Preview	https://deploy-preview-8277--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 95 (🟢 up 5 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 yourNetlify site configuration.

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base(5c253a8) 87.71% compared to head(9af90d0) 87.72%.

@@           Coverage Diff           @@##             main    #8277   +/-   ##=======================================  Coverage   87.71%   87.72%           =======================================  Files         397      397             Lines       13963    13971    +8       Branches     4061     4065    +4     =======================================+ Hits        12248    12256    +8  Misses       1403     1403             Partials      312      312

Aside: could you please not force push PRs? It's a small thing, no worries, but fromhttps://typescript-eslint.io/contributing/pull-requests:

Reasoning: GitHub is not able to track changes across force pushes, which makes it take longer for us to perform incremental reviews

Aside: could you please not force push PRs? It's a small thing, no worries, but fromhttps://typescript-eslint.io/contributing/pull-requests:

Oh OK! Sorry about that. I was making the review difficult. 😅

No worries at all 😄 TIL I (re-)learned thatgh pr checkout has a--force.

@JoshuaKGoldberg Oops, Maybe this rule should report error on this cases?

https://github.com/typescript-eslint/typescript-eslint/actions/runs/7744772276/job/21119385280?pr=8277

• https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/website/src/components/config/ConfigTypeScript.tsx#L38

// group: Record<string, ConfigOptionsType>group[category]??={heading:category,fields:[],};

I don't know how that comment got hidden - but, yes - could you take a look please actually?

(I'm between things atm)

@JoshuaKGoldberg I made a pr for fixing it (#8336)
I thinks the lint error was false positive of no-unnecessary-condition. And the false positive fixed in#8249.