Tuist, in recent versions, sorts targets alphabetically rather than in the order they were added, as it did previously.
Therefore, in the target list, if there are many feature targets, it becomes inconvenient to find the app target.
Have you been able to identify which version caused this regression? That would help us in tracking down the issue.
When you mention sorting, do you mean sorting in the scheme list or somewhere else … ?
Sorting in the list of targets
I haven’t looked for the version where sorting appeared yet, since maybe it was done on purpose
I believe this was done to make the hashing more stable, but we can make the hashing stable by sorting the targets closer to where hashing happens. So, I’d say no, this wasn’t a conscious change.
This has been bothering me for several releases now as well, and I’m finally having to bite the bullet on an upgrade for my most complicated project so I decided to hunt it down. The change from definition-based sorting to alphabetical sorting happened in 4.16.0, and it seems most likely caused by this PR.
Would love if there could be a change back, or at least an option to use the defined order. I used to have my targets ordered by “type”: app, embedded binaries (extensions, watch app, etc.), feature targets, tests. As @emelyanovkirill said, putting it all alphabetically makes it more difficult to find what I need.