Open darrenldl opened 1 year ago
Thanks! This looks like an issue for @SimonJF -- I'll let you have a look first.
I believe @SimonJF is away for a bit. It's totally plausible to me that we might not be doing the right thing here, especially since this may have been tested in a time/place where GMT/UTC would have been the default. Probably we should also be providing a variant of intToDate that takes an explicit timezone.
Thanks, will take a look when I’m back! I think @jamescheney is likely right in that we are probably relying on an underlying UK time assumption for intToDate. Wonder what happens on the client, too.
Hello,
Context
I am the main developer of Timedesc - a modern alternative to
calendar
essentially, and I was poking around at packages which depend oncalendar
out of curiosity to see if it causes issue in other packages (there have been known issues in ISO8601.ml etc).(Interesting language! I like the language design quite a lot.)
Problem
For time zones outside of UTC, conversion from date time to timestamp and back yields a different date time.
Europe/London
Australia/Sydney
UTC (this is fine)
I will say I don't know if I'm using links correctly, or how relevant this might be to links, or how the interaction with DB works etc.