-
Notifications
You must be signed in to change notification settings - Fork 20
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
Consider qunit/no-assert-equal-boolean #366
Comments
Personally I'm not sure |
We did the equivalent of this for phpunit in mediawiki-codesniffer recently. |
(But that's with strict typing, as you point out.) |
Enables: * no-async-module-callbacks * no-compare-relation-boolean * no-hooks-from-ancestor-modules * no-nested-tests * require-object-in-propequal Disables: * no-arrow-tests * no-assert-equal-boolean (#366)
What happened in codesniffer? |
The above patch will not enable this rule, but will disallow |
Enables: * no-async-module-callbacks * no-compare-relation-boolean * no-hooks-from-ancestor-modules * no-nested-tests * require-object-in-propequal Disables: * no-arrow-tests * no-assert-equal-boolean (#366)
Shall we say that this is good enough and mark this as Resolved? |
This rules suggests
assert.true( foo )
overassert.strictEqual( foo, true )
:https://github.com/platinumazure/eslint-plugin-qunit/blob/master/docs/rules/no-assert-equal-boolean.md
Both check for a strict equality to
true
.The text was updated successfully, but these errors were encountered: