When using expect() for writing asserting, some of the assertion are using properties as the mean for calling assert.
For example
expect(foo).to.exist
JSLint/JSHint will complain about such code, since it expects an assignment or function call.
Hiding a function call, behind getting a property can be sweet but in tests, it leads to such warnings.
I know that one can use assert calls, or not use JSHint/JSLint or configure JSHint/JSLint to ignore such warnings, but I just want to know what is your feeling about this problem.
When using expect() for writing asserting, some of the assertion are using properties as the mean for calling assert.
For example
expect(foo).to.exist
JSLint/JSHint will complain about such code, since it expects an assignment or function call.
Hiding a function call, behind getting a property can be sweet but in tests, it leads to such warnings.
I know that one can use assert calls, or not use JSHint/JSLint or configure JSHint/JSLint to ignore such warnings, but I just want to know what is your feeling about this problem.