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
Disallow and potentially autofix assertions like:
assert.true(foo === 1); assert.false(foo !== 1);
Solutions:
no-boolean-equality
checkBooleanAssertions
My preference is 2 to avoid creating a highly redundant new rule.
The text was updated successfully, but these errors were encountered:
no-ok-equality
Similar to #170, I agree with doing option 2 for now, although long-term I do want to rename the rule.
Sorry, something went wrong.
Successfully merging a pull request may close this issue.
Disallow and potentially autofix assertions like:
Solutions:
no-boolean-equality
. But this would be highly redundant with the no-ok-equality rule.checkBooleanAssertions
to no-ok-equality (default false until next major version).My preference is 2 to avoid creating a highly redundant new rule.
The text was updated successfully, but these errors were encountered: