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
First I thought it might be a bug, but after checking the involved code, it looks like it's the expected behavior. Also, found that regular JS Date objects have a similar behavior.
But I wonder if there is any workaround, configuration parameter, or method to avoid the year inference to actually parse years < 99. As IMHO it's a valid use case.
As reference this is the behaviour of the java-time Clojure library in this aspect:
When trying to parse dates that contain years with 2 digits (years <= 99), or leading zeros (ej "0099") ,the library automatically adds the century.
First I thought it might be a bug, but after checking the involved code, it looks like it's the expected behavior. Also, found that regular JS
Date
objects have a similar behavior.But I wonder if there is any workaround, configuration parameter, or method to avoid the year inference to actually parse years < 99. As IMHO it's a valid use case.
As reference this is the behaviour of the java-time Clojure library in this aspect:
This issue in the Google Closure library might also be interesting.
Thank you
The text was updated successfully, but these errors were encountered: