Replies: 1 comment 4 replies
-
There's no official approach to how you should structure your projects as it depends on your usecase and on your preferences. Personally, I would avoid |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What problem or need do you have?
Hello!
I would like to ask some questions about using Tuist to implement componentization of iOS projects.
Component directory structure
Tuist is very flexible, so what is the officially recommended componentized directory structure? So far I have found the following situations:
Project.swift
file of the main project, each component has a separate folder.Project.swift
file of the main project is not in the root directory. It is in its own App folder, and each component has a separate folder.Projects
folder.These solutions confused me as a first-time user of Tuist, and I didn’t know which one was the most correct and best. I hope to follow the official best practices, but I'm not sure if this exists.
Workspace‘s
projects
In the "Workspace.swift" file, do I need to pass all projects (those with implicit dependencies, like in the example mentioned below) to "projects"?
In the example of ios_workspace_with_dependency_cycle,
projects
contains all projects. But not all are referenced in ios_app_with_transitive_project.After my practice, I found that even if all projects are not included,
.xcworkspace
can still be generated and compiled. So if all items don't need to be included, are there any hidden risks to be aware of with this approach?macOS version
14.4.1 (23E224)
Tuist version
4.9.0
Xcode version
15.3
Beta Was this translation helpful? Give feedback.
All reactions