-
Notifications
You must be signed in to change notification settings - Fork 236
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
test.each no-done-callback false positive in version 24.1.2 #710
Comments
I just had the same issue. After having a quick look at the rule implementation, it seems the logic is to check the number of arguments of the test function. But for |
The list of test cases can also contain a callback, so I don't think that would work. it.each([
[1, () => 2],
])(...); I think jest is also checking the number of arguments: https://github.com/facebook/jest/blob/f9132f9106e3f1b3ae6f81d1f36222055c3fe111/packages/jest-each/src/bind.ts#L81-L83 |
🎉 This issue has been resolved in version 24.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Very similar to #709, but there is still a false positive when the test function has 2 arguments.
Plugin version: 24.1.2
Last working version: 24.1.0
Rule jest/no-done-callback has false positives with test.each
The text was updated successfully, but these errors were encountered: