Module migrate 

Moves a calendar tum_google_sync kept in Google Calendar over to an Apple (iCloud) calendar, which tum_apple_sync keeps in sync from then on.

• Events the Google sync created are recognized by the uid: marker at the end of their description. They’re stored under the same uid the Apple sync uses, so it keeps updating them just like the Google sync did.
• Whatever was changed by hand in Google Calendar comes along: notes in the description, a seat number in the location, reminders and colors. Events deleted in Google stay deleted.
• Events added to the calendar by hand are copied as well, recurring ones including their moved and cancelled occurrences.
• Nothing is ever deleted, neither in Google nor in the Apple Calendar. Events that already exist in the Apple Calendar are skipped unless MigrationOptions::overwrite is set.

See migrate_google_to_apple to run it.

Structs

MigrationOptions

Controls what migrate_google_to_apple does.

Functions

migrate_google_to_apple

Copies the Google calendar that tum_google_sync kept over to an Apple Calendar. See the module documentation for what it does exactly.

move_exams_to_exam_calendar

Moves the exams that are in the main calendar over into the exam calendar (see AppleCalendar::with_exam_calendar) - the ones migrate_google_to_apple put there, or the ones created before there was an exam calendar.