hyzyla
commented
1 month ago @schwjustin I can implement only the "run" command without building, but to run something, you need to build it separately. I think it will not work faster than executing the "Build & Run (Launch)" command because it will work the same way, just only one part of this command
I suppose, Xcode works faster here with "Run" acrtion because they have the rebuild process running constantly to show errors in Xcode, and when you press the "Run" button in Xcode, it already has a warm build cache. My VS Code extension is completely built on top of the xcodebuild command, which doesn't have functionality like incremental rebuilding. One way to have incremental building in the extension is to reimplement the Xcode build system on my own, but that is too big of a task for me right now. Another option is to explore xcode build service proxies, that allow to hook into build process, but I'm not sure it's flexible enough to add support for incremental build
schwjustin
Is it possible to add just a run command that will also override the current run like you can do in xcode? If I could map this to cmd+R I wouldn't need to keep switching back and forth from vs code to xcode, it's just much faster to run in xcode then to wait for the build & run command from sweetpad currently.
Also, when I do use the build & run sweetpad command with my simulator already the running the app, it asks me to terminate or restart the process in the bottom left corner of vs code which is also not convenient (in xcode the first time you try to start a run with an active run it asks you if you want to override it but there's a checkmark to never ask again - I don't think asking is even necessary tbh).