doc: 'assert' description contains backwards actual/expected

Documentation for assert describes:

assert(value[, message]), assert.ok(value[, message])
Tests if value is truthy. It is equivalent to assert.equal(true, !!value, message).

But assert.equal parameters are actual value first, then expected value. The documentation should read:

assert(value[, message]), assert.ok(value[, message])#
Tests if value is truthy. It is equivalent to assert.equal(!!value, true, message).

@birnam

@birnam mind to make a Pull Request for it? I'd gladly review it!

Sure -- PR: #3533

This was landed in 471aa5a

Navigation Menu