-
Notifications
You must be signed in to change notification settings - Fork 837
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong timezone used for implicit year/month/day #807
Comments
Month and day have the same problem. I'm intending to use this to parse times (e.g. Fortunately,
gives the correct/expected result (
|
@murrayju how did you get See my results:
|
or you used methods like '.getDate()', '.getFullYear()', '.getDate()' which resulted to this:
You should use .format() to get correct values:
|
I used This is a bug report, not a question. |
I finally succeeded to reproduce it, thanks for reporting. This is how it can be reproduced:
|
This is a duplicate of #874, closing this for now. |
This is probably only an issue around new year's day. If I parse a date like the following:
My expectation is that it will implicitly use the current year in the
America/Denver
timezone (which is currently 2019). Instead, it seems to be assuming the year that it is in GMT, resulting in the date being parsed as2021-01-01T00:00:00.000Z
which is a year in the future, instead of today.The text was updated successfully, but these errors were encountered: