We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Do you want to request a feature or report a bug? Bug
What is the current behavior? expect-matcher rule doesn't detect the missing matcher inside arrow function expression:
expect-matcher
it("test", () => expect("something"))
If the current behavior is a bug, please provide the steps to reproduce.
parserOptions: ecmaVersion: 6 plugins: - jasmine env: jasmine: true rules: jasmine/expect-matcher: 2
What is the expected behavior? The expected error message is:
Expect must have a corresponding matcher call. (jasmine/expect-matcher)
It does work correctly for statement block though:
it("test", () => { expect("something")) }
And when the matcher is not being called:
it("test", () => expect("something").toBe)
Please mention your node.js, eslint-plugin-jasmine and operating system version. Windows 10 x64 Node v8.14.0 [email protected] [email protected]
The text was updated successfully, but these errors were encountered:
fix(expect-matcher): verify expect() is in MemberExpression
d0aa0a6
fixes tlvince#174
Successfully merging a pull request may close this issue.
Do you want to request a feature or report a bug?
Bug
What is the current behavior?
expect-matcher
rule doesn't detect the missing matcher inside arrow function expression:If the current behavior is a bug, please provide the steps to reproduce.
What is the expected behavior?
The expected error message is:
It does work correctly for statement block though:
And when the matcher is not being called:
Please mention your node.js, eslint-plugin-jasmine and operating system version.
Windows 10 x64
Node v8.14.0
[email protected]
[email protected]
The text was updated successfully, but these errors were encountered: