Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

StyleShit
Copy link
Contributor

@StyleShit StyleShit commented May 15, 2025

Closes #742

@StyleShit StyleShit force-pushed the fix/742-get-property-identifier-node-await-expression branch from 87f42ea to bb3ced4 Compare May 15, 2025 11:20
@StyleShit StyleShit changed the title fix: no-wait-for-side-effects doesn't detect await expression fix: no-wait-for-side-effects doesn't detect await expressions May 15, 2025
Copy link

codecov bot commented May 15, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 96.25%. Comparing base (26d360e) to head (eb4c965).
Report is 17 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1008      +/-   ##
==========================================
- Coverage   96.27%   96.25%   -0.03%     
==========================================
  Files          46       47       +1     
  Lines        2472     2483      +11     
  Branches     1025     1031       +6     
==========================================
+ Hits         2380     2390      +10     
- Misses         92       93       +1     

☔ 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.

Copy link
Member

@Belco90 Belco90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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).

@Belco90 Belco90 changed the title fix: no-wait-for-side-effects doesn't detect await expressions fix(no-wait-for-side-effects): detect await expressions May 16, 2025
@Belco90 Belco90 added the bug Something isn't working label May 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Failure to detect no-wait-for-side-effects when used in conjunction with await
2 participants