Is there a documented future plan for adding ability to make a package
having dependency to only a submodule of another package?
Some libraries may want to split their full API into logical components and
provide a way to integrate them individually. As an example, the popular
networking library AFNetworking
<https://github.com/AFNetworking/AFNetworking> has components like
'Serialization', 'Security', 'NSURLSession' and 'UIKit' in its podspec, and
users can depend on just a particular component rather than depending on
full API.
I'm pretty sure there will be need for that feature in future and you most
probably talked about that before. I just want to know if there is an
existing concrete architectural plan.
Is there a documented future plan for adding ability to make a package having dependency to only a submodule of another package?
Some libraries may want to split their full API into logical components and provide a way to integrate them individually. As an example, the popular networking library AFNetworking <https://github.com/AFNetworking/AFNetworking> has components like 'Serialization', 'Security', 'NSURLSession' and 'UIKit' in its podspec, and users can depend on just a particular component rather than depending on full API.
I'm pretty sure there will be need for that feature in future and you most probably talked about that before. I just want to know if there is an existing concrete architectural plan.
Best,
Yes, we plan it. If you open a ticket we’ll use that to track the feature.