also looking at this
iOS Phase 9: calendar and contacts — ratchet 53 → 48
#91
6 files
+5708
-1
| @@ -29,6 +29,15 @@ const bridge_mobile_motion = ; | ||
| 29 | 29 | const bridge_mobile_imagepicker = ; |
| 30 | 30 | const bridge_mobile_filepicker = ; |
| 31 | 31 | const bridge_mobile_contactpicker = ; |
| 32 | const bridge_mobile_calendar = ; | |
| 33 | const bridge_mobile_contacts = ; | |
| 34 | // `bridge_mobile_speech.zig` is deliberately NOT in the chain. Its | |
| 35 | // capability_actions table is empty — the two speech actions were researched | |
| 36 | // in full and left with the Swift shim — so a module here would iterate, | |
| 37 | // return UnknownAction, and cost a comparison to serve nothing. Keeping it in | |
| 38 | // the chain would also read as coverage it does not provide, which is the | |
| 39 | // habit this migration exists to break. The file stays as the record of that | |
| 40 | // decision and of the Swift behaviour a future port has to match. | |
| 32 | 41 | |
| 33 | 42 | const objc = objc_runtime.objc; |
| 34 | 43 | |
| @@ -239,6 +248,8 @@ const mobile_bridges = .{ | ||
| 239 | 248 | bridge_mobile_imagepicker.ImagePickerBridge, |
| 240 | 249 | bridge_mobile_filepicker.FilePickerBridge, |
| 241 | 250 | bridge_mobile_contactpicker.ContactPickerBridge, |
| 251 | bridge_mobile_calendar.CalendarBridge, | |
| 252 | bridge_mobile_contacts.ContactsBridge, | |
| 242 | 253 | }; |
| 243 | 254 | |
| 244 | 255 | /// Narrow an arbitrary handler error to one the page's error codes can express. |