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 found that you're using toLocaleTimeString() method to write timestamp
It might cause problems in some cases (ie if different locale is set on different environments and local developers machine)
So, for example, if locale is set to en-us timestamp looks like 4:32:46 PM.765
I think it's better to use ISO formatted time, ie 16:32:46.765
The text was updated successfully, but these errors were encountered:
envilogger
added a commit
to envilogger/mag-fallback
that referenced
this issue
Dec 20, 2015
Yes, using toLocaleTimeString method isn't good idea.
But for mag-fallback module I think it will be enough to have only time in the message. I will try to implement it using getUTC* methods.
Hi
I found that you're using
toLocaleTimeString()
method to write timestampIt might cause problems in some cases (ie if different locale is set on different environments and local developers machine)
So, for example, if locale is set to
en-us
timestamp looks like4:32:46 PM.765
I think it's better to use ISO formatted time, ie
16:32:46.765
The text was updated successfully, but these errors were encountered: