Complete recurrence editing and calendar preferences
This commit is contained in:
@@ -65,10 +65,12 @@ and the user must sync before retrying. A calendar-owned task,
|
||||
`govoplan_calendar.sync_due_caldav_sources`, can run due sources in a worker or
|
||||
cron-style scheduler.
|
||||
|
||||
This is not yet a full CalDAV network server. Scheduling inbox/outbox behavior,
|
||||
CalDAV server endpoints, UI credential management, and full user-facing
|
||||
recurrence editing remain follow-up work. The backend now includes a free/busy
|
||||
API primitive for scheduling and appointment modules.
|
||||
Calendar exposes collection and credential management, sync status/actions,
|
||||
durable per-user view preferences, recurrence expansion, detached occurrence
|
||||
overrides, instance/series editing, and a free/busy API primitive for scheduling
|
||||
and appointment modules. It is not yet a CalDAV network server: external clients
|
||||
cannot use GovOPlaN itself as their CalDAV endpoint, and scheduling inbox/outbox
|
||||
delivery remains owned by the scheduling and mail integration work.
|
||||
|
||||
## Development
|
||||
|
||||
|
||||
Reference in New Issue
Block a user