-
-
Notifications
You must be signed in to change notification settings - Fork 2.8k
chore(eslint-plugin): no-confusing-void-expression getConstraintInfo
#10586
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
base: main
Are you sure you want to change the base?
Conversation
Moves to using `getConstraintInfo` internally in the `no-confusing-void-expression` rule. Also fixes a bug this uncovered, where `AwaitExpression` nodes were actually untested and not supported in the type constraint checks. This is because we passed `node` (the `AwaitExpression` itself), rather than the thing being awaited (`node.argument`). By passing the `argument`, we check its type instead.
Thanks for the PR, @43081j! 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!
To edit notification comments on pull requests, go to your Netlify site configuration. |
View your CI Pipeline Execution ↗ for commit 59a8b4a.
☁️ Nx Cloud last updated this comment at |
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #10586 +/- ##
=======================================
Coverage 86.90% 86.90%
=======================================
Files 446 446
Lines 15502 15508 +6
Branches 4516 4519 +3
=======================================
+ Hits 13472 13478 +6
Misses 1675 1675
Partials 355 355
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Moves to using
getConstraintInfo
internally in theno-confusing-void-expression
rule.Also fixes a bug this uncovered, where
AwaitExpression
nodes were actually untested and not supported in the type constraint checks.This is because we passed
node
(theAwaitExpression
itself), rather than the thing being awaited (node.argument
). By passing theargument
, we check its type instead.PR Checklist
getConstraintInfo
internally #10569