~whynothugo/pimsync#155: 
Alternative logic for collection names

Implement an alternative storage for collection names using the second-to-last segment from the path component of the URL.

This is specifically for Google's server implementation.

See: https://whynothugo.nl/journal/2025/03/04/design-for-google-caldav-support-in-pimsync/

Status
REPORTED
Submitter
~whynothugo
Assigned to
No-one
Submitted
2 months ago
Updated
a month ago
Labels
0:missing-feature 3:vstorage

~whynothugo added 3:vstorage 2 months ago

~whynothugo 2 months ago

Also need a relevant config setting.

~whynothugo 2 months ago

From alternative notes:

given a USER_PRINICPAL and a CALENDAR, the ID is the difference of both:

- USER_PRINCIPAL: /users/hugo/calendars/
- CALENDAR: /users/hugo/calendars/work
- ID: work

In google's case, we have a slash, which we replace with a dash:

- USER_PRINCIPAL: /users/hugo/calendars/
- CALENDAR: /users/hugo/calendars/work/events
- ID: work.events

This scales to any "unusual" caldav server

~whynothugo added 0:missing-feature a month ago

Register here or Log in to comment, or comment via email.