test(eslint-plugin): [no-misused-promises] add test cases for spread args

[kirkwaiblinger]

PR Checklist

• Addresses an existing open issue: fixes Bug: [no-misused-promises] An array of promises passed with spread (...args) syntax is not checked #5744
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Implements the action items detailed in #5744 (comment).

Only functional change is to add test cases for the concern in the issue.

[typescript-eslint]

Thanks for the PR, @kirkwaiblinger!

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.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	e174685
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65d8c92c9a943f000778f1de
😎 Deploy Preview	https://deploy-preview-8493--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 98 (🟢 up 8 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 your Netlify site configuration.

[nx-cloud]

☁️ Nx Cloud Report

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

---

✅ Successfully ran 31 targets

• nx test eslint-plugin
• nx test visitor-keys
• nx run types:build
• nx test typescript-eslint
• nx run repo-tools:postinstall-script
• nx test eslint-plugin --coverage=false
• nx test utils
• nx test typescript-estree
• nx test type-utils
• nx test rule-schema-to-typescript-types
• nx test scope-manager
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint
• nx test parser
• nx test eslint-plugin-internal
• nx test repo-tools
• nx test ast-spec
• nx test visitor-keys --coverage=false
• nx test utils --coverage=false
• nx test type-utils --coverage=false
• nx test typescript-estree --coverage=false
• nx run-many --target=lint --parallel
• nx test typescript-eslint --coverage=false
• nx test scope-manager --coverage=false
• nx test rule-schema-to-typescript-types --coverage=false
• nx test repo-tools --coverage=false
• nx test parser --coverage=false
• nx test eslint-plugin-internal --coverage=false
• nx test ast-spec --coverage=false
• nx run-many --target=typecheck --parallel
• nx run repo-tools:generate-configs
• nx run integration-tests:test

---

Sent with 💌 from NxCloud.

[auvred]

#8534 is going to add support for unions. And it looks like it's going to make changes exactly on these very lines. So, to avoid merge conflicts, what do you think about reverting these changes in favor of #8534

[kirkwaiblinger]

makes sense! reverting and resolving conflicts

[auvred]

🚀 LGTM!

Aside: since this PR doesn't make any bug fixes, I think we should rename it from fix(eslint-plugin): ... to test(eslint-plugin): ... . What do you think?