Directory structure like this (standard):
- top - Projects - Project1 - Project.swift - Project2 - Project.swift - Project3 - Project.swift - Tuist - Config.swift - ProjectDescriptionHelpers <etc> - Templates <etc>
When I “tuist edit” inside a project1 directory the manifest workspace that opens up shows:
- Manifests - Project2 - Project.swift - Project3 - Project.swift - Project.swift - Workspace.swift
It comes across as a little odd that the project structure here is a little different from the directory structure (I would have probably listed all three projects at the same level as folders, each with a Project.swift inside), but it is definitely workable.
What surprised me is that while the Workspace.swift file from the top-level is included, the Config.swift from the Tuist directory is not, and also missing is the Setup.swift from the top-level.
For Config.swift I would argue it directly impacts the code generated by “tuist generate” and so it should be included here. Doing so also makes it a lot easier to edit with syntax coloring and compiler checking.
The argument is a little harder to make for Setup.swift, but I’d like it to be included as well.