The in-progress v1.3.0 PR (#1) adds --availability support for add event and update event — great addition. However, eventToDict() doesn't include the availability property in its output, so there's no way to read back the free/busy status of events via list events or show event.
Request: Add event.availability to the dictionary returned by eventToDict() in EventKitManager.swift. Something like:
switch event.availability {
case .busy: dict["availability"] = "busy"
case .free: dict["availability"] = "free"
case .tentative: dict["availability"] = "tentative"
case .unavailable: dict["availability"] = "unavailable"
case .notSupported: dict["availability"] = "notSupported"
@unknown default: dict["availability"] = "unknown"
}Use case: I'm using ekctl to read my Exchange work calendar for planning and review workflows. Knowing which events are "busy" vs "free" vs "tentative" is important for identifying actual availability windows.
The in-progress v1.3.0 PR (#1) adds
--availabilitysupport foradd eventandupdate event— great addition. However,eventToDict()doesn't include theavailabilityproperty in its output, so there's no way to read back the free/busy status of events vialist eventsorshow event.Request: Add
event.availabilityto the dictionary returned byeventToDict()inEventKitManager.swift. Something like:Use case: I'm using ekctl to read my Exchange work calendar for planning and review workflows. Knowing which events are "busy" vs "free" vs "tentative" is important for identifying actual availability windows.