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
I recently ran into a similar issue and was able to debug it by importing is-equal/why manually and running it through. Turns out the prototype of the two objects I was comparing where different, causing is-equal to return false and create an assertion error. I'm rolling in here a bit late with this, but you might want to try that in the future if you run into issues like these.
That being said, I also think it'd be great to see error messages use whyNotEqual rather than spitting out the value of both objects in their entirety.
I'm getting what appears to be a bogus error:
It would be great is failed assertions would use
whyNotEqual
to report the issue:https://www.npmjs.com/package/is-equal#want-to-know-why-two-values-are-not-equal
The text was updated successfully, but these errors were encountered: