-
Notifications
You must be signed in to change notification settings - Fork 81
Closed
Description
Currently, NaN values always result in CHANGE, even though nothing changed. Technically in JS, NaN !== NaN, so I understand that there is an argument for this behavior. However, I think that having a CHANGE entry on EVERY diff when an object contains NaN is noise, and therefore unexpected / undesirable behavior.
I propose treating NaN values as equivalent, resulting in the following:
diff({ testNaN: NaN }, { testNaN: NaN }) === [] // trueCheshireCaat, micalevisk, wc-matteo and FluentCoding
Metadata
Metadata
Assignees
Labels
No labels