React-calendar-timeline: OnMove gives NAN for new starttime
If you use date as values for item starttime and item endtime, then OnItemMove will give you NaN as result for the new start time.
If you pass unix timestamps then things work.
forki
👍1
All 5 comments
I ran into a similar issue.
- Used a Date object for starttime and endttime.
- onCanvasClick was returning a Nan.
Solved with using unix timestamps in milliseconds for starttime and endttime
gachavez
on 12 May 2018
I feel like this timeline should only support unix timestamps in ms as the input. marshaling between strings, Date object, Moment and milliseconds is a pain.
mcMickJuice
on 28 May 2018
👍2
Simplify, simplify and simplify!
Fully agree.
jabidof
on 28 May 2018
Fix should go out in next release
mcMickJuice
on 12 Jun 2018
Fixed in 0.17.0
mcMickJuice
on 12 Jun 2018
Was this page helpful?
0 / 5 - 0 ratings
Related issues
capt-obvious
路
6Comments
stahlmanDesign
路
4Comments
b5imply
路
3Comments
ivikash
路
5Comments
rosanzheng
路
3Comments
Most helpful comment
I feel like this timeline should only support unix timestamps in ms as the input. marshaling between strings, Date object, Moment and milliseconds is a pain.