explicitly named "date" property in filteredData?

[gassc]

I'm really liking this tool and the way it abstracts away some of the boilerplate required to get a D3 visualization like this up and running. So, thank you.

---

I think I'm noticing an issue that may be related to this line where filteredData is established (but I'm not entirely sure):

EventDrops/src/index.js

Line 88 in 62328de

withinRange(d.date, dateBounds)

Does this mean that the event data objects must always have a date property, with that name exactly?

What I'm seeing:

If my event objects don't explicitly have a date property (in my case my data has a datetime property instead), the resulting filteredData object's data property is empty while the fullData property is complete (so nothing appears on the timeline).

If I run a data transformation ahead of time, renaming my datetime property to date, then things work as expected.

Running a transformation ahead of time is not an issue at all (and in fact I need to do that anyway, just like in the demo), but I just wanted to confirm what I'm seeing.

[jpetitcolas]

Good catch! We indeed should use the config.drop.date function here. It definitively worths a PR! :)

[jpetitcolas]

Released in 1.0.2.