diff --git a/docs/api-wishlist.md b/docs/api-wishlist.md index a6a9612..89b22c8 100644 --- a/docs/api-wishlist.md +++ b/docs/api-wishlist.md @@ -8,9 +8,17 @@ Done items move to the bottom. - **List the calendars.** Ids, slugs and names are hardcoded in `lib/calendars.ts` and must be kept in step with `calendarNames` in `events.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 / history.** Every save already writes a row to `event_versions`, and delete is a +- **Restore.** Every save already writes a row to `event_versions`, and delete is a `DELETED` version - 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_versions` with who + (`version_created_by_user_id`) and when - but `PUT /move/:id` only runs + `UPDATE events SET calendar_id = …`: who moved an event, when, and from which calendar is recorded + nowhere (`event_versions` has no calendar column). Found 2026-11-08; deferred by the user. Fix: + add `calendar_id` to `event_versions` and 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 on `event_versions`. - **Don't return deleted events** from the admin feed (or behind a flag). They arrive as rows with every field `null` except `status`, and the client has to know to drop them. - **Richer recurrence.** `repeatFrequency` goes out as `RRULE:FREQ=` with no interval, end