Repository navigation
Replies: 1 comment 1 reply
|
Thanks, this is a clear report and you have found a real gap. Confirming what is actually true today, because it is worse than it looks. There is exactly one destination per user, not per connection and not per event type. Choosing a destination unsets it everywhere else, first across your calendars and then across your accounts, and the write path resolves it with There is no good workaround, which is why this is worth building. Connecting the same CalDAV account four times does not help, because destination is a single per-user slot and the connections would fight over it. Splitting into four users would work but means four logins to run one person's week. Moving events by hand after each booking is what you are doing now. You are not asking for anything exotic. Cal.com ships this: destination calendars can be set globally and then overridden per scheduling link in the advanced options, which is the same shape you are describing. So it is a reasonable expectation rather than an unusual request, and that is a large part of why I want to build it. How I want to build it, narrowly. An override that is event-type aware, stored per event type and per host, falling back to your normal destination when nothing is set. The important part is not the table, it is that destination is resolved in exactly one place, so the write path cannot half-know about the override. That single resolution point is also where the failure mode gets handled: if the chosen calendar is deleted or the connection is revoked, it falls back to your default and says so in the log rather than silently writing nowhere. Two things it will deliberately not touch. Conflict checking stays exactly as it is, since checking all four calendars already works for you. And reschedule and cancel already follow the provider holding the event, so they are unaffected by design. One thing that would help: you said you work on your own with no team. If this is always going to be a single-host setup for you, say so, because it keeps the first slice simple, and I would rather confirm that than assume it. No timeline committed, but this is tracked and it is a feature I want rather than a favour. |
Uh oh!
There was an error while loading. Please reload this page.
Hi there! thanks for calnode (v.0.13.0).
I work at multiple locations (4) and have a calendar for each. On my phone, each calendar has it's own colour code and thus easy to see where I need to be next. I work on my own and currently without a team. All my calendars are managed via one single CALDAV account.
I've created different event types for each location (ie. Location X: 1 hr, Location Y: 1hr) but since I use a single CALDAV account I can only choose one destination for any of the events I've created. Checking all four calendars for conflicts works great.
Would it be possible in the future to choose the destination calendar based on the event type? Or is there a better solution for my scenario?
Thanks
All reactions