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
We currently ignore null, undefined and NaN easing parameters. I understand why we should ignore null and undefined, but ignoring NaN seems unnecessary. (I suppose it’s consistent with how d3-arrays ignores values, though.)
The text was updated successfully, but these errors were encountered:
mbostock
changed the title
Don’t ignore NaN parameters.
Don’t ignore NaN parameters?
Nov 19, 2015
The problem with ignoring NaN here is it suggests we should ignore NaN everywhere, which is burdensome and of dubious value. In d3-shape, for example, I ignore null and undefined interpolation parameters, but not NaN ones.
We currently ignore null, undefined and NaN easing parameters. I understand why we should ignore null and undefined, but ignoring NaN seems unnecessary. (I suppose it’s consistent with how d3-arrays ignores values, though.)
The text was updated successfully, but these errors were encountered: