CalendarEvent

A calendar event, as a calendar app reads one: a title, and its days or its times.

Use it to send an invitation or an .ics entry. For when something repeats on its own, use RecurrenceRule.

Shape

Write every field when you build one, and give a field that isn't required as none.

Its parts keep these rules, and a value that breaks one fails with the rule's name:

• days_or_times: first_day and last_day with no start, end or zone, or start, end and zone with no days
• last_day_not_before_first: last_day >= first_day
• end_after_start: end > start
• recurrence_from_start: recurrence starts on first_day, or at start in zone

Example

CalendarEvent {    summary: "Team lunch"    first_day: "2026-12-18"    last_day: "2026-12-18"    start: none    end: none    zone: none    location: none    description: none    recurrence: none}

text.parse(raw, as: CalendarEvent) reads one from text that comes from outside. Text that isn't one at all fails malformed.

Good to know

• An event has either days (first_day and last_day) or times (start, end and zone), never both.
• last_day is included, even though calendar files write the day after.
• == tells you whether two are the same. < and list.sort_by don't take it, so sort by one of its parts instead.

In JSON

An object of its parts, in a request, a response or json.write:

{"summary":"Christmas Day","first_day":"2026-12-25","last_day":"2026-12-25","start":null,"end":null,"zone":null,"location":null,"description":null,"recurrence":null}{"summary":"Half-term walk","first_day":"2026-10-24","last_day":"2026-10-26","start":null,"end":null,"zone":null,"location":"Keswick, Cumbria","description":"Boots; maps\nFlask","recurrence":null}{"summary":"Wedding anniversary","first_day":"2024-02-29","last_day":"2024-02-29","start":null,"end":null,"zone":null,"location":null,"description":null,"recurrence":"DTSTART;VALUE=DATE:20240229\nRRULE:FREQ=YEARLY"}

When you read one, a field that isn't required may be left out, or sent as null.

Details