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
I can plug my data with the ~ operator but the date interpreted is wrong. It compute to something like "1635-05-02 00:00:00".
Thank to your test suite I found that it's a problem with how dayJs parse the string (https://day.js.org/docs/en/parse/string). I was able to fix it by adding a call to parseInt() before the value is given to dayJs.
Would you be interested in a PR with those changes ?
EDIT: Thinking a bit more about it, it could cause trouble if the string is a ISODate, I'm going to try and see how both cases can be handled.
This discussion was converted from issue #161 on March 07, 2022 23:03.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi,
First thank you for this great plugin !
I have an api that return time serie data as json objects, like this:
I can plug my data with the
~
operator but the date interpreted is wrong. It compute to something like "1635-05-02 00:00:00".Thank to your test suite I found that it's a problem with how dayJs parse the string (https://day.js.org/docs/en/parse/string). I was able to fix it by adding a call to parseInt() before the value is given to dayJs.
Would you be interested in a PR with those changes ?
EDIT: Thinking a bit more about it, it could cause trouble if the string is a ISODate, I'm going to try and see how both cases can be handled.
Thanks for your attention.
Beta Was this translation helpful? Give feedback.
All reactions