-
Notifications
You must be signed in to change notification settings - Fork 9
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
Time Zones do not Account for DST #15
Comments
In the meantime I have adjusted my database to store formatted local time instead of timestamps so that I just don't have to worry about converting between them. I was able to do this comfortably because my project is tied to a local physical location, so data always originates from and is consumed in the same timezone. Birl being Gleam native is really nice, but with the complexity of time zones, maybe it does not make sense for Birl to support them when the ecosystem project is still so new (I'm talking about named time zones, like "America/New_York", not offset times). Maybe a package should be created that is wrapper for an Erlang lib that handles getting the offset from named time zones, then it could be used with Birl once the proper offset is known. |
yeah, I've been trying to solve this issue for a while, but I just couldn't find enough free time to do it. |
Yeah now that the package is v1, I agree we can't just remove it. Maybe adding gleam's |
The following code
produces
2024-03-26T07:28:36.000-05:00
when it should produce2024-03-26T08:28:36.000-04:00
because America/New_York is in EDT time right now, which has the offset of -04:00. Between sometime in March and sometime in November each year in America the timezone offset values changes to an hour ahead because of Daylight Saving Time.The text was updated successfully, but these errors were encountered: