Imaging having such a complicated project structure that agents don't even TRY to edit it, instead telling you where to click to add it manually.
And not even making a cli to automated that.
JS devs cannot comprehend.
Imaging having such a complicated project structure that agents don't even TRY to edit it, instead telling you where to click to add it manually.
And not even making a cli to automated that.
JS devs cannot comprehend.
@alex yaeh but it also requires an xcode window reload, way too annoying.
Really, no need to optimize this. how often do you really add a dependency?
I started a project recently and picked tuist. I had the same complaints about the files, so what I ended up doing is having all my code a in a single spam package that tuist depends on. I am basically using it solely for Xcode project generation, which removes the binary caching niceties.
I did end up writing a script to add all my spam targets into the workspace after generation, and I sometimes have to “save” the Paxkage.swift in Xcode if the project is regenerated, but I only need to regenerate if I add an new spm module.
@alex @jefflewis @pedro I asked claude to take an existing project as template, adapt it to my new thing and that’s all I need. The only thing agents are not good at is bootstrapping.
Once you have your project file with v77 folder format that syncs for disk changes you only need manual changes for changing swift package dependencies, which is rare