-
Notifications
You must be signed in to change notification settings - Fork 228
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
[no-jasmine-globals] Verify Jasmine pending() global usage #156
Labels
Comments
I think I'm running into basically this problem. With a parameter named function foo(success, fail) {
fail();
} I get "Illegal usage of |
Yeah, definitely! Wanna send a PR? You can see #155 for how to implement it 🙂 |
jdelStrother
added a commit
to jdelStrother/eslint-plugin-jest
that referenced
this issue
Nov 17, 2018
Prior to this, similarly named local variables & parameters would trigger the no-jasmine-globals warning Fixes jest-community#156
jdelStrother
added a commit
to jdelStrother/eslint-plugin-jest
that referenced
this issue
Nov 18, 2018
Prior to this, similarly named local variables & parameters would trigger the no-jasmine-globals warning Fixes jest-community#156
🎉 This issue has been resolved in version 22.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Originally posted by @SimenB in #155 (comment)
This issue is a follow-up to check that the
no-jasmine-globals
rule doesn't have the same issues reported in #149.The text was updated successfully, but these errors were encountered: