Closed UrsMetz closed 7 years ago
You're absolutely right! Thanks for bringing this to my attention again! I fixed that and released v0.13.3. Please give it a try and let me know if it wasn't what you were expecting! I'll close this until again. :)
@moll just gave it a try and it works as expected, thanks for the fast fix and release! :-)
When comparing objects using
eql
and the actual object has a property that isNaN
the diff of the failed assertion is misleading: the following assertionresults in this message:
The root cause is that
json-stringify-safe
convertsNaN
tonull
.