Thanks for the PR, @abrahamguo!

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.

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	d8509be
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/66d62c16df293c0008bcc03d
😎 Deploy Preview	https://deploy-preview-8556--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: 90 (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 Report

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

📂 See all runs for this CI Pipeline Execution

Sent with 💌 from NxCloud.

Marking as a draft pending #8722's resolution.

Conflicts resolved and ready for re-review!

I am not clear why the one test is failing. It works locally for me.

It's from the CI job that runs tests with the project service enabled:

Copying the failure here:

  ● restrict-template-expressions › valid › const msg = `arg = ${new URLSearchParams()}`;

    assert.strictEqual(received, expected)

    Expected value to strictly be equal to:
      0
    Received:
      1
    
    Message:
      Should have no errors but had 1: [
      {
        ruleId: '@rule-tester/restrict-template-expressions',
        severity: 2,
        message: 'Invalid type "URLSearchParams" of template literal expression.',
        line: 1,
        column: 22,
        nodeType: 'NewExpression',
        messageId: 'invalidType',
        endLine: 1,
        endColumn: 43
      }
    ]

You can directly test that file in packages/eslint-plugin with TYPESCRIPT_ESLINT_PROJECT_SERVICE=true yarn jest restrict-template-.

Hmm, looks like setting TYPESCRIPT_ESLINT_PROJECT_SERVICE=true causes it to bypass the tsconfig-withdom.json set in restrict-template-expressions.test.ts.

I've worked around this by ensuring that (similar to the new examples in the docs page) the unit tests only refer to the Error type, which is available with or without the DOM types.
URL and URLSearchParams are not shown in the docs code examples, nor in the unit tests, since they require DOM types in order to work properly.