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
Proposal: Use normal linux timestamps externally instead of custom timestamps. (still use our format internally)
We currently use normal epoch timestamps / 1000 in order to have more bearable date internally and in json logic.
However using them outside, e.g. in forms, you always have to convert between normal stamps and internal stamps.
The text was updated successfully, but these errors were encountered:
So, the difference is that Linux timestamps are in seconds, while Javascript timestamps from date.now() are in milliseconds.
If I understand you correctly, only timestamps in seconds should be used in the JSON and for the interfaces/functions of the engine, correct? I would agree.
exactly so every function that is exposed externally should return timestamps in milliseconds and expect to get results in milliseconds.
It may also check if the value given is already in seconds.
Proposal: Use normal linux timestamps externally instead of custom timestamps. (still use our format internally)
We currently use normal
epoch timestamps / 1000
in order to have more bearable date internally and in json logic.However using them outside, e.g. in forms, you always have to convert between normal stamps and internal stamps.
The text was updated successfully, but these errors were encountered: