Repeating Events

[thedekel]

Repeating Events

[thelastnode]

This is non-trivial. For example, what if I want to delete a recurring series, or edit the recurring series and then edit a specific event.

Look at Google Calendar or Outlook's implementation of this stuff - when the user edits anything recurring, the option should be presented to edit the series or the instance.

Changes to the series should affect all events, and changes to the instance should only override the specific fields they modify. For example, if I have a recurring series, and I edit the time of one event, then the title of the series, the title change should be reflected everywhere, but that one event should retain the new time.

[thedekel]

that's why the repeating event is a new object and not just a modified event object.

Changes to the "repeating event" object is reflected in future events (since new events aren't generated until the week of the event), but past events are left unchanged. Since the events themselves are separate from the "repeating event" object, we can change them without affecting future events.

Although, we may want to include some sort of link to the parent "repeating event" from a generated event. The use case is that an org admin wants to change a repeating event, but has mistakenly opened a specific event.