Waldemar Kornewald11/13/2023, 12:17 PM
Waldemar Kornewald11/13/2023, 2:52 PM
or match on the path to apply some config to all modules within a subfolder (when you have two or more levels). This is a convention that everyone can see and follow at first glance (it's self-documenting) and it requires no copy-paste with 50 modules. That's similar to
which is also self-documenting because it's based on file/directory naming. Templates may have their uses, but we have quite complicated and large projects with many different teams and the convention based solution works really well and helps giving you a better overview because you open just one file and see all the modules e.g. that export an XCFramework or have something else in common. This overview is missing with the templates solution. Also creating templates has its own friction. Most developers just won't do it. They'll be used to editing individual module files and start copy-paste solutions. Forcing people to apply rules from the root makes them think in better generalizations because the friction is minimal and the better overview helps with generalizing.
Anton Prokhorov11/13/2023, 5:38 PM