Closed SebastianKrupinski closed 1 week ago
All modified and coverable lines are covered by tests :white_check_mark:
Project coverage is 23.48%. Comparing base (
9d1688c
) to head (991402f
). Report is 30 commits behind head on main.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Can you elaborate why skipping the first (or 0 position) solves the issue please? :pray:
Can you elaborate why skipping the first (or 0 position) solves the issue please? 🙏
Morning, sure,
This code actually process the first position, instead of skipping it, the original code, skipped transition 0, which in certain time zones is needed for time zones with static transitions.
Here is a example of how Mexico City time zone was being generated:
Before:
BEGIN:VTIMEZONE
TZID:America/Mexico_City
X-MICROSOFT-CDO-TZID:37
END:VTIMEZONE
After:
BEGIN:VTIMEZONE
TZID:America/Mexico_City
X-MICROSOFT-CDO-TZID:37
BEGIN:STANDARD
TZOFFSETFROM:-0600
TZOFFSETTO:-0600
TZNAME:CST
DTSTART:19700101T000000
END:STANDARD
END:VTIMEZONE
The Mexico City timezone has a single static transition which was being skipped originally, and because the "BEGIN:STANDARD" was missing the timezone was never applied to the event, showing the event off by the amount of the timezone offset.
/backport to stable4.7
/backport to stable5.0
Resolves: https://github.com/nextcloud/calendar/issues/6476
Testing: See issue ticket for details.