Resolve "Make timezone field optional in personal event mutations"
Closes #1104 (closed)
Merge request reports
Activity
added part::backend type::bug + 1 deleted label
I think I understand the issue now. Currently the frontend never sends a timezone. But the backend needs the timezone in case the event is recurring. Therefore it needs to optionally send a timezone if it's a recurring event.
I will implement this now.
What I do not get is when the PersonalEvent is mutated how does the backend communicate the current timezone to the frontend? Either I do not understand or there is something missing.
Also why does a single event not need a timezone?
A single event doesn't need a timezone as we store it with the correct UTC offset (something that is supported by Postgres), but for recurring events we need the timezone (due to summer and winter time changes). Currently, the correct timezone isn't communicated to the frontend, but the datetime is returned with the correct offset.
added 18 commits
-
6fc20bd3...f75940f0 - 16 commits from branch
master - 1ce5afa2 - Pass timezone to backend if recurring personal-event
- edfeb7ad - Enable removal of optional recurrence for personal-events
-
6fc20bd3...f75940f0 - 16 commits from branch
mentioned in commit 1cc55b52