docs(proto): occurrence_date is a local date, not a UTC key #203
No reviewers
Labels
No labels
adr
android
area/calendar
area/design-system
area/i18n
area/jobs
area/offline
area/server
area/testing
bug
ci
duplicate
enhancement
help wanted
invalid
notifications
question
reliability
security
severity/low
severity/medium
tracking
web
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
eagraiclainne/app!203
Loading…
Reference in a new issue
No description provided.
Delete branch "docs/occurrence-date-zone"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #198.
The comment on
Event.occurrence_datecalled the slot key UTC. It neverwas.
domain.ExpandEventOccurrencesformats it from a time alreadyconverted into the zone the request carried, and
validSlotparses it backwith
ParseInLocationagainst that same zone.A client that believed the comment would compute the key in UTC and,
anywhere east or west of it, address a different day — splitting or
cancelling the wrong occurrence. The new wording also keeps the key apart
from
Event.time_zone, which is a real but unrelated field the reminderticker reads.
Comment only, plus the regenerated artifacts that carry it.
🤖 Generated with Claude Code
Test report
Coverage: 26.7%
Updated by the check workflow · commit
b074c386a8Android test report
Coverage: 3.0% of lines
Updated by the android workflow · commit
b074c386a809451c05ccb074c386a8