{"id":45267,"date":"2024-10-07T13:27:30","date_gmt":"2024-10-07T17:27:30","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=45267"},"modified":"2024-10-24T14:17:17","modified_gmt":"2024-10-24T18:17:17","slug":"xcode-16-folders-and-groups","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/10\/07\/xcode-16-folders-and-groups\/","title":{"rendered":"Xcode 16 Folders and Groups"},"content":{"rendered":"

Sarah Reichelt<\/a> (Mastodon<\/a>):<\/p>\n

\n

In Xcode 16, project files and folders are arranged differently in the Project navigator. What used to be a group<\/strong> is now a folder<\/strong>, and this simple change has some interesting effects. At first, I was against the new scheme - in fact in my SwiftUI for Mac 2024<\/a>\narticle, I specifically recommended reverting back to the old group method. But after doing some more reading and testing, I think the answer is not so clear cut.<\/p>\n

[…]<\/p>\n

At a first glance, there are two differences: the order of the files & folders and the color of the folder icons. A less obvious difference is that in Xcode 15, I can drag files around to arrange them in the order I prefer. In Xcode 16, I can’t do that. I can drag files into or out of folders, but I can’t move them around at the same level.<\/p>\n

[…]<\/p>\n

This points out the fundamental difference between the two approaches: groups<\/strong> are an artificial construct that is stored in the project files. Usually, this mirrors the file and folder structure in Finder, but it doesn’t have to. When you use folders<\/strong>, Xcode is reading the file and folder structure directly from the Finder.<\/p>\n

[…]<\/p>\n

The big difference is in source control, especially if you’re working with other people. When every file addition, deletion or move also changes the project file, you have a much greater chance of getting a merge conflict.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n