d3.min and d3.least don't always ignore nulls about d3 HOT 4 CLOSED

You’re probably using an old version of D3?

from d3.

As for the other cases, this:

d3.min(['5', '10', null, '2'], (d) => +d)

is equivalent to this:

d3.min(['5', '10', null, '2'].map((d) => +d))

is equivalent to this:

d3.min([5, 10, 0, 2])

hence it returns zero.

And likewise for d3.least, it doesn’t care that the element is null, it cares whether the return value of the given accessor is null. So if you coerce null to zero in your accessor, and zero is the least value, then d3.least will return the corresponding element which is null.

from d3.

Yes. Thank you. I know this is the expected behavior. The problem is that the accessor is not really being used to access anything, but to coerce and change values in the dataset, which can lead to cryptic code. Mislead by an example of mine where I used +d to coerce strings, my student spent a day trying to fix a bug and fixed it after removing nulls from her dataset. She had understood that extent should ignore nulls, but wasn't aware that they were being coerced.

from d3.

Yes, I recommend that you apply type coercion as early as possible — ideally when the data is loaded, say by using d3.autoType in conjunction with d3.csv, or Observable’s FileAttachment helper with typed: true. If you defer type coercion until later, there is much more surface area for these problems.

from d3.