feat: edit recurring events, this-one or the whole series #74
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!74
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/recurring-event-edit"
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?
Final part of #61: recurring events become editable on both surfaces, with a this-one-or-the-series choice. Closes the event-editing half of #61.
Non-recurring events already edit in place (#71 web, #73 Android). This adds editing for a repeating occurrence: the event sheet offers a scope choice —
SplitOccurrencesplits the occurrence into a one-off child, then the form edits that child. Only that instance changes.events.read) and edits it; the change lands on every occurrence. The repeat rule itself stays fixed (editing recurrence is still a separate flow).Web:
EventDetailgains the scope picker;CalendarwireseditOne(split) andeditSeries(read).Android:
EventSheetgains the picker;MoreRepositoriesgainssplitForEdit/eventForEdit, mapping the returned event into the row the form prefills from.Verified:
make checkpasses (web tsc/build,:app/:datacompile, Go tests, web + Android i18n catalogs synced for the two new strings).Part of #61 (the last piece).
🤖 Generated with Claude Code
Test report
Coverage: 27.7%
Updated by the check workflow · commit
710402a7953817392a99710402a795Android test report
Updated by the android workflow · commit
710402a795