CalendarEvent

A calendar event (RFC 5545's VEVENT): an all-day event's first and last days, both included, or a timed event's local start and end and its zone, never both, with what it is called and, where it has them, where it is, what it is about and how it repeats. Written as a VEVENT, an all-day event's DTEND the day after its last.

Time and calendar; not ordered; since Jadpo 0.1.0.

Make one

Build one from its fields, CalendarEvent { summary: ... }.

text.parse(raw, as: CalendarEvent) reads one from its text; text that isn't one at all fails malformed, such as "".

Its parts keep these rules; 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

Fields

Text, JSON and storage

text.from writes its canonical text, the one form text.parse reads back. JSON sends an object of its parts.

It is stored in 9 columns, each named for the field, _ and its suffix. This is BEGIN:VEVENT\nDTSTART;VALUE=DATE:20240229\nDTEND;VALUE=DATE:20240301\nSUMMARY:Wedding anniversary\nRRULE:FREQ=YEARLY\nEND:VEVENT:

Shown to people

text.format(value, locale:) shows it to people in their locale.

With locale: Locale.en_gb:

Operations

It has the contract's own operations: text.parse, text.from, text.format, json.read, json.write and ==. It isn't ordered, so < and sorting don't take it. Every standard type meets one contract says how they work.