-
Notifications
You must be signed in to change notification settings - Fork 162
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
Respect timezone of Luxon DateTime instance when rendering an allday event #592
Comments
Ah cool, I didn't know you could save the time zone in a |
🎉 This issue has been resolved in version 7.1.0-develop.1 🎉 The release is available on:
Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 7.1.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
I store dates as ISO timestamps, like
2024-03-17T00:00:00.000+01:00
. When I add an all day event to a calendar like in the following example, it is rendered as20240316
in the ical format, but20240317
would be my expectation.This does not happen, when the
cal
object is given a fixed timezone, likecal.timezone('Europe/Zurich')
. But that only works if allDateTime
instances are in that same timezone – which they might not be in my case. Therefore, my instances ofICalCalendar
don't have a timezone set, yet still I expect that the timezone which is embedded in theDateTime
instance is respected.I've created a PR with just some test (for now) to further explain my situation as unit tests: #591
In order to fix it, I'm unsure whether it needs to be addressed in
event.ts#toString()
or intools.js#formatDate()
.The text was updated successfully, but these errors were encountered: