-
Notifications
You must be signed in to change notification settings - Fork 603
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
parseDate is an hour off with DST date #689
Labels
Comments
rxaviers
added a commit
to rxaviers/globalize
that referenced
this issue
Feb 21, 2017
- Handle special case when target date and today date are in different DST rules; Fixes globalizejs#689
rxaviers
added a commit
to rxaviers/globalize
that referenced
this issue
Feb 23, 2017
- Handle special case when target date and today date are in different DST rules; Fixes globalizejs#689
mwistrand
pushed a commit
to mwistrand/i18n
that referenced
this issue
Mar 14, 2017
Implements a workaround for a Globalize.js bug (globalizejs/globalize#689) that incorrectly parses date strings when the resulting date follows a different rule from today's date (e.g., the parsed date is in standard time while today's date is in daylight savings time).
3 tasks
mwistrand
pushed a commit
to dojo/i18n
that referenced
this issue
Mar 15, 2017
* Implement a workaround for a Globalize.js bug (globalizejs/globalize#689) that incorrectly parses date strings when the resulting date follows a different rule from today's date (e.g., the parsed date is in standard time while today's date is in daylight savings time). * Temporarily pin Globalize.js version to prevent the `fixParsedDate` method from breaking on the next release of Globalize.js.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @rxaviers,
parseDate
appears to have a bug in parsing a DST date.My environment:
Here's a Node script that demonstrates the problem. Note that the summer date is 5:32am PDT, but after globalize parse it's 4:32am PDT:
Output:
I have a hunch that if this were summer right now, it would be the winterDate failing. 😄
The text was updated successfully, but these errors were encountered: