'truthy' and 'falsy' should be chainable properties.

Especially since the description for ok actually uses the word truthy.

[codewithkristian]

Realize this is closed, but giving this a 👍 because I also think that “truthy”/“falsy” is more clear than “ok”.

[jamestalmage]

Consider this fairly common scenario: Some API’s return a result object which may or may not have a property error. The presence of said property indicates that there was … an error. So while writing a test where I expect an error, I might do something like this:

var result = someActionThatShouldProduceAnError();
expect(result.error).to.be.ok;

That is potentially confusing to someone who isn’t familiar with chai. The following is easier to understand.

expect(result.error).to.be.truthy

If you google “javascript ok” vs. “javascript truthy”, I think it shows that truthy is a better choice than ok.

Chai is full of redundant syntax, so rejection on that basis seems arbitrary.

• above, gt, greaterThan
• equal, equals, eq
• include, contain

I could be persuaded to give up on falsy in favor of not.truthy, but I’d ask you to reconsider rejecting the idea in its entirety.