-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Read and write time zone ID when updating CalDAV availability #29318
Read and write time zone ID when updating CalDAV availability #29318
Conversation
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
d3eeb85
to
6c76e2d
Compare
The data from https://github.com/touch4it/ical-timezones/tree/master/lib/zones seems to never have been updated since the start of the project, so we'll probably encounter issues soon enough. |
Fair point, but do we have alternatives? |
I ran their generator. I don't see any changes except formatting differences with quoted object key. |
That's because it doesn't update the .ics files, only the js files. The I've used https://github.com/libical/vzic/ (which seems active) to generate the |
Is there anything I could help with? |
Rebasing? :) |
Nah, that's non blocking for this PR anyway. |
Tiny bug/limitation of #27466 Signed-off-by: Christoph Wurst <[email protected]>
6c76e2d
to
6301531
Compare
|
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.
Minor request, otherwise looks good!
Signed-off-by: Christoph Wurst <[email protected]>
6301531
to
a34f94d
Compare
tested and it works |
Tiny bug/limitation of #27466
Now the timezone id is read from the previous value but also encoded in the newly saved icalendar value. If no time zone was set before it will still fall back to the auto detected one.
How to test
/settings/user/groupware
On master: you see the auto detected time zone again
On this branch: time zone is the one you previously stored
Without this fix reloading the page and saving the availability will shift your times by the drift of the time zone.
I tested this against an availability rule created by Apple Calendar.
The only diff to their format is that we don't generate the DST vs standard time recurrence rules within the timezone component but I guess we would need some data for this that we currently don't have.done with the help of https://www.npmjs.com/package/icalzone