You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One of the projects we are working on has a couple of pods, these are currently quite heavy and are slowing up the build times for the whole project. We are currently migrating the project to a more modular architecture. There are 6 feature modules in total and 2 are actually using these pods. Ideally we would want to use the approach of creating an abstraction around the pod lib using a struct based approach and then splitting the live version into one swift package and the struct abstraction + mock into another as suggested in the episode. The we would be able to build the app using the mock/noop version whilst developing and for real releases use the live versions. However since the live version requires pods (which cannot be forked and ported into a swift package) we are a bit stuck on the most optimal solution.
What would your thoughts be?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
One of the projects we are working on has a couple of pods, these are currently quite heavy and are slowing up the build times for the whole project. We are currently migrating the project to a more modular architecture. There are 6 feature modules in total and 2 are actually using these pods. Ideally we would want to use the approach of creating an abstraction around the pod lib using a struct based approach and then splitting the live version into one swift package and the struct abstraction + mock into another as suggested in the episode. The we would be able to build the app using the mock/noop version whilst developing and for real releases use the live versions. However since the live version requires pods (which cannot be forked and ported into a swift package) we are a bit stuck on the most optimal solution.
What would your thoughts be?
Beta Was this translation helpful? Give feedback.
All reactions