Reminder repeat data

[ap]

Thanks for this tool. I’m very happy to have stumbled across it while looking for a way to back up post-Ventura Reminders.app data, which no longer has a built-in Export function (thanks, Apple). Thankfully reminders show-all -f json lets me get just about everything back out.

The one thing I’m missing is the data from the Repeat and End Repeat fields. I’d very much like to have that also, because I stay on top of various household chores and such using a fairly long list of repeating reminders, whose repetition info would be somewhat onerous to have to figure out from scratch. (Currently my only backup option seems to be to keep a screenshot of that list…)

[keith]

yea if you want to PR adding some fields for that to the json format that seems reasonable to me

[ap]

I’m afraid I don’t know Swift or any of the relevant APIs so all I can do at the time of this writing is dump a request in your lap. 🙂 (The whole reason I’m now using your tool is so I don’t have to learn all of that!)

[mgiugliano]

@keith May I ask you where to find the documentation of the existing "fields"? I would love to add these features and starting from the very basics of Reminders.app would be precious to me.

[keith]

EKReminder is the primary class: https://developer.apple.com/documentation/eventkit/ekreminder#

and that inherits from EKCalendar item which has a lot more stuff https://developer.apple.com/documentation/eventkit/ekcalendaritem

[jdtsmith]

A agree this would be nice to have. I think each repeating EKReminder (via EKCalendar) has a recurrenceRule, which is of type EKRecurrence. That object type has quite a few fields specifying the recurrence.

[mgiugliano]

A agree this would be nice to have. I think each repeating EKReminder (via EKCalendar) has a recurrenceRule, which is of type EKRecurrence. That object type has quite a few fields specifying the recurrence.

See my fork. I considered (my own) need to providing a JSON string as an input and used there the recurring field. I am eager to see what @keith thinks about that and I am happy to polish it or improve it further.