In a hotel booking app's multi-module Tuist project, the Feature modules import each other's implementation modules directly, so changing one rebuilds everything. How would you change the dependency structure?
Split each Feature into an Interface module holding only protocols and models and an implementation module, have Features depend on each other's Interface only, and assemble and inject the implementations in the App target.
Build and distributionShort answerExpert
A team on an app with more than a hundred modules is drowning in project.pbxproj…
#tuist
Build and distributionShort answerAdvanced
How do you set up a third-party library through SPM in a project that Tuist generates?
#tuist
Build and distributionShort answerAdvanced
The interviewer asks about setting up a modular project with Tuist from scratch. Walk…
#tuist
Build and distributionShort answerBasics
A clean build of an ecommerce iOS app runs past 15 minutes and both CI and local builds…
#modules