2.7 KiB
2.7 KiB
API wish list
Changes to the API that would help this app, collected during the rewrite. None of them block it. Done items move to the bottom.
Open
- List the calendars. Ids, slugs and names are hardcoded in
lib/calendars.tsand must be kept in step withcalendarNamesinevents.router.ts. An endpoint would make a new calendar a data change. - All calendars in one request. The admin list makes five parallel requests on every load.
- Restore. Every save already writes a row to
event_versions, and delete is aDELETEDversion - so "Wiederherstellen" and a change history are possible without schema changes, only endpoints are missing. The UI's delete dialog says it can't be undone "hier". - Log moves. Create, edit and delete each append a full version to
event_versionswith who (version_created_by_user_id) and when - butPUT /move/:idonly runsUPDATE events SET calendar_id = …: who moved an event, when, and from which calendar is recorded nowhere (event_versionshas no calendar column). Found 2026-11-08; deferred by the user. Fix: addcalendar_idtoevent_versionsand write a version on move too. - Show the history in the UI. With an endpoint like
GET /calendar/events/:id/versions, the edit sheet could list who changed what and when. Today the UI shows only "Erstellt von" and "Zuletzt geändert von"; the full history is only reachable via SQL onevent_versions. - Don't return deleted events from the admin feed (or behind a flag). They arrive as rows with
every field
nullexceptstatus, and the client has to know to drop them. - Richer recurrence.
repeatFrequencygoes out asRRULE:FREQ=<value>with no interval, end or count. With those, recurrence could become editable in the form (today only Geburtstage getYEARLY, automatically). - A failed update should not be a 200.
PUT /calendar/events/:idanswers 200{"message": "0 rows were updated"}when nothing was written; the client treats that body as an error. A 404/409 would say it properly. - Explicit time zones. The API relies on the process running in Berlin time for the iCal output
(see the API's
docs/calendar-ical.md). SettingTZexplicitly at start-up, or formatting with an explicit zone, would remove the dependency on the server's configuration. ORGANIZERas a cal-address (ORGANIZER;CN=Name:mailto:…) instead of a bare name.DB_PORTfor every pool. Only the admin pool reads it; calendar, feedback and tickets always use 3306.
Done
- iCal escaping, line folding and CRLF;
text/calendarcontent type (API branchfeature/calendar-ical-escaping-subscriptions, 2026-09-28). GET /calendar/events/subscriptionsfor the "Abonnieren" dialog (same branch).