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
It seems that parse("yesterday at 5") does not interpret 5 as time (i.e. hours). It would be nice if this was the case, as this seems a natural way of expressing time of day. From a brief look at the code, it looks like 5 on its own is too general to be interpreted as an indication of hours, however, I think that at could be used to pinpoint the meaning of the integer number.
I understand that in locales that do not use the 24h clock, the simple 5 might be ambiguous (see #210), but at the moment this also does not work in locales that use the 24h clock. For example in the de_DE locale, gestern um 5 and gestern um 17 do not get parsed correctly and the default time of the locale is used.
The text was updated successfully, but these errors were encountered:
It seems that
parse("yesterday at 5")
does not interpret5
as time (i.e. hours). It would be nice if this was the case, as this seems a natural way of expressing time of day. From a brief look at the code, it looks like5
on its own is too general to be interpreted as an indication of hours, however, I think thatat
could be used to pinpoint the meaning of the integer number.I understand that in locales that do not use the 24h clock, the simple
5
might be ambiguous (see #210), but at the moment this also does not work in locales that use the 24h clock. For example in thede_DE
locale,gestern um 5
andgestern um 17
do not get parsed correctly and the default time of the locale is used.The text was updated successfully, but these errors were encountered: