First of all, you guys are doing an outstanding job for the community. And this mini library will greatly benefit everyone. Thank you
I do have a question. I’m sure you guys have considered this, but did you feel at any time that this library could be released outside of TCA?
Take for instance, swift-case-paths. I was really happy to see it being moved out of TCA and added as a dependency. Now, for swift-case-paths it makes sense to live as a dependency, you need it to complement Swift and enhance TCA.
Contrasting with CoreLocation, only a small subset of users would use it in comparison to the thousand of developers that are already full on developing with it (myself included).
Let’s say someone would like to implement support for some FileProvider, an Image Picker or a Document Picker for the iCloud drive, Siri support, or some other framework/api, would these fit in TCA?
One thing that comes to mind is RxSwift, where there is a community driven account for projects that enhance RxSwift’s experience. The ComposableCoreLocaliton could serve as a great jump start for something like this I believe.
Unless CoreLocation is a really specific use case that really needs to be in TCA, and I’m just not seeing it. I may be way of here.
Anyways, what are your thoughts on this?
Thank you again for the all great contributions you guys are making, enabling everyone to write better apps!
TCA in the hands of a junior developer would make an experienced developer from a couple years back really sweat to keep up ahah