Description
The iCal export handles 30+ properties per component. The JSCal export handles only: uid, title, description, start, duration/due/estimated_duration, time_zone, status, priority, color, locale, privacy, free_busy_status, show_without_time, categories, keywords.
Missing JSCalendar-mapped properties include:
- `locations` (from location/geo)
- `recurrenceRules` (from recur/rrule)
- `excludedRecurrenceRules` (from exdates)
- `participants` (from attendees/organizer)
- `links` (from attachments/url)
- `relatedTo`
- `created`, `updated`
- `sequence`, `recurrenceId`
- `replyTo`, `method`
These are all standardized JSCalendar properties. Currently they fall through to the vendor property handler and are emitted under their gnomon field names rather than their proper JSCalendar names. This violates `r[model.export.preserve+2]`: "Mapped properties MUST be translated into their target-format equivalents."
Description
The iCal export handles 30+ properties per component. The JSCal export handles only: uid, title, description, start, duration/due/estimated_duration, time_zone, status, priority, color, locale, privacy, free_busy_status, show_without_time, categories, keywords.
Missing JSCalendar-mapped properties include:
These are all standardized JSCalendar properties. Currently they fall through to the vendor property handler and are emitted under their gnomon field names rather than their proper JSCalendar names. This violates `r[model.export.preserve+2]`: "Mapped properties MUST be translated into their target-format equivalents."