-
Notifications
You must be signed in to change notification settings - Fork 21
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
fix(core): using correct timezone when parsing dates #1355
Conversation
Deployed to https://test-deployment-pr-1355.herokuapp.com/ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
🎉 This PR is included in version 3.8.2-master.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 3.8.2 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
To test the issue on the current version:
UTC-0600
ChildSchoolRelation
(child -> education)This is because
new Date("2022-01-01")
is interpreted as UTC time. Converting this toUTC-0600
results in 6pm the day before (2021-12-31
).The very simple fix to this is to instead use a different date constructor:
new Date(2022, 0, 1)
is interpreted as first of January 2022 in the local time.Visible/Frontend Changes
--
Architectural/Backend Changes
date-only
andmonth
are interpreted with the local timezone