You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 4, 2020. It is now read-only.
AssertionError: expected [Promise] to be rejected: expected CustomError {} to match CustomError {}
rejectedWith no longer works with custom errors because it calls match which then does an isPlainObject call which checks the object prototype. This is a breaking change from earlier versions. Is there a reason you are requiring the prototype to be Object.prototype or null?
Node.js 10.14.0
Should.js version 13.2.3
Repro here: https://repl.it/@cloverb/WeirdWeepySpheres
AssertionError: expected [Promise] to be rejected: expected CustomError {} to match CustomError {}
rejectedWith
no longer works with custom errors because it callsmatch
which then does anisPlainObject
call which checks the object prototype. This is a breaking change from earlier versions. Is there a reason you are requiring the prototype to beObject.prototype
ornull
?https://github.com/shouldjs/should.js/blob/master/should.js#L3168 -> https://github.com/shouldjs/should.js/blob/master/should.js#L4055 -> https://github.com/shouldjs/should.js/blob/master/should.js#L1429
The text was updated successfully, but these errors were encountered: