Repository navigation
Description
From discussion #241 (xenonone1). Cal.com parity: their v1.3 ships destination calendars globally with a per-scheduling-link override in advanced options, so this is expected behaviour, not an exotic ask.
Problem
Destination is resolved as exactly one calendar per user. SetDestination unsets connection_calendars.is_destination and calendar_connections.is_destination for the whole user, then sets one. The write path resolves with WHERE user_id = ? AND is_destination = 1 LIMIT 1.
Consequence: a host with four locations under one CalDAV account cannot have four destinations. There is no workaround - connecting the account four times does not help because destination is a single per-user slot, and separate users means separate logins.
Proposed shape
Per (event_type_id, user_id) override row pointing at a provider + calendar_id. Falls back to the user's normal destination when no row exists.
Boundary, stated so it does not creep: this is a destination override and nothing else. It does not affect conflict checking (that already unions across selected calendars), and it does not touch reschedule or cancel (those follow the provider holding the event, per #58).
Critical implementation constraint
Destination must be resolved in exactly ONE place, used by the single write path. There is precedent for getting this wrong: the "I chose it and nothing changed" bug in calselect.go, where the account was resolved first and the calendar second, so a calendar choice in another account did nothing. Adding an event-type dimension to a multi-site resolution makes that class of bug more likely, not less.
Failure mode to design
If the chosen calendar is deleted, or the connection is revoked, fall back to the user's default destination and log it. Never write nowhere silently.
Tests that matter
- Override wins over the user default
- No override behaves byte-identically to today
- Revoked/deleted calendar falls back to default and logs
Open question
Reporter says he works alone with no team. Confirm single-host is the only case for him before trimming the first slice.
Discussion: #241
Activity
pullfrog commentedon Nov 10, 2026