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
Turning number of seconds into usable representation (unix timestamp / moment.js) requires unnecessary effort (if timezone offset or DST has to be taken into account)
Possible solution
Always use a unix timestamp representation, both for specifying inputTime and also for return value.
Workaround
The text was updated successfully, but these errors were encountered:
I actually disagree, or think this should be optional. The headaches that this introduces from a timezone perspective alone is enough to complicate this library a great deal.
Users may or may not use the moment library. Even if they use moment library you can convert the returned epoch to the local timezone, and then you can easily convert it using moment methods.
Problem
Possible solution
Always use a unix timestamp representation, both for specifying inputTime and also for return value.
Workaround
![image](https://cloud.githubusercontent.com/assets/5816039/14500681/4b9b1950-01a3-11e6-8ddc-817c1f867603.png)
The text was updated successfully, but these errors were encountered: