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
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})===[]// true
The text was updated successfully, but these errors were encountered:
Currently,
NaN
values always result inCHANGE
, 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 aCHANGE
entry on EVERY diff when an object containsNaN
is noise, and therefore unexpected / undesirable behavior.I propose treating
NaN
values as equivalent, resulting in the following:The text was updated successfully, but these errors were encountered: