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
We should create a rule which ensures that equality checks are not performed as the assertion argument of assert.ok and assert.notOk.
assert.ok
assert.notOk
Ideally, the rule would suggest a better assertion to use instead:
assert.ok(a === b)
assert.strictEqual(a, b)
assert.ok(a == b)
assert.equal(a, b)
assert.ok(a !== b)
assert.notStrictEqual(a, b)
assert.ok(a != b)
assert.notEqual(a, b)
assert.notOk(a === b)
assert.notOk(a == b)
assert.notOk(a !== b)
assert.notOk(a != b)
The text was updated successfully, but these errors were encountered:
New: no-ok-equality rule. (refs #7)
864d04d
Error message still needs to be improved.
Update: Enhanced rule error messages for no-ok-equality. (fixes #7)
b3638a2
No branches or pull requests
We should create a rule which ensures that equality checks are not performed as the assertion argument of
assert.ok
andassert.notOk
.Ideally, the rule would suggest a better assertion to use instead:
assert.ok(a === b)
would becomeassert.strictEqual(a, b)
assert.ok(a == b)
would becomeassert.equal(a, b)
assert.ok(a !== b)
would becomeassert.notStrictEqual(a, b)
assert.ok(a != b)
would becomeassert.notEqual(a, b)
assert.notOk(a === b)
would becomeassert.notStrictEqual(a, b)
assert.notOk(a == b)
would becomeassert.notEqual(a, b)
assert.notOk(a !== b)
would becomeassert.strictEqual(a, b)
assert.notOk(a != b)
would becomeassert.equal(a, b)
The text was updated successfully, but these errors were encountered: