Closed nunogoncalves closed 1 year ago
Hi Nuno, Thanks for the PR. I'll have to defer to @krzysztofzablocki on this one as it is his package. There are other alternatives though: Create a third package that has Inject and HotReloading as dependencies and your users would only have to add that. Another alternative to the HotReloading Swift Package would be migrating to the new InjectionLite re-write which brings in less "baggage" and should be equivalent.
Hi John. Thanks for your answer. :)
Create a third package that has Inject and HotReloading as dependencies and your users would only have to add that
This exactly what we're doing. :)
thanks
This MR adds customization support for injection bundles.
Reading InjectionIII documentation, we read in Variations on using the InjectionIII app section:
Thinking about this, and trying to find ways to decrease the number of things my colleagues need to do, me and @andredp came up with this solution.
This way, we can share the iOS bundle in our project repo, and that way nobody needs to do any additional work to setup Hot Reloading in their machine. For other platforms, this would also works, as long as we keep the bundle names according to list.
Hopefully this is a good adition to this project. Looking forward to hear from you! :)