fix(no-wait-for-side-effects): detect await expressions

[StyleShit]

Closes #742

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.29%. Comparing base (26d360e) to head (1e27b58).
Report is 20 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #1008      +/-   ##
==========================================
+ Coverage   96.27%   96.29%   +0.01%     
==========================================
  Files          46       47       +1     
  Lines        2472     2483      +11     
  Branches     1025     1027       +2     
==========================================
+ Hits         2380     2391      +11     
  Misses         92       92              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Belco90]

Thanks for addressing this bug!

I see code coverage went down, so Codecov complains. Can you add extra tests for no-wait-for-multiple-assertions? It's indirectly affected (see more details).

[StyleShit]

Thanks for addressing this bug!

I see code coverage went down, so Codecov complains. Can you add extra tests for no-wait-for-multiple-assertions? It's indirectly affected (see more details).

there was a redundant isExpressionStatement check in the code that filtered await expressions before they have been checked

On a side note - the CI is so fast, I like it! 🚀

[Belco90]

On a side note - the CI is so fast, I like it! 🚀

I'm glad you like the CI speed! We can do even better, hopefully we can switch to vitest soon.

[github-actions]

🎉 This PR is included in version 7.2.2 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀