Use swift commands in SPM projects #248

m-housh · 2024-11-17T20:55:18Z

m-housh
Nov 17, 2024
Sponsor

It would be nice if building and testing in an SPM package used swift build and swift test instead of the xcodebuild commands that require a scheme and workspace.

The downside of using xcodebuild (which very well may be my skill issue) is having to constantly open Xcode and update the package scheme when adding new targets whereas swift build and swift test generally just work as expected.

When working inside of Xcode I believe this is managed for you / new targets get added to the default <project>-Package scheme, however when I'm working in nvim this doesn't occur, which leads to a couple of issues. Firstly LSP doesn't really work until you add the target to the scheme and build and secondly your project still builds however you may not be building all the targets that you think you are.

At any rate, this is a great project and I really appreciate your work.

wojciech-kulik · 2024-11-17T21:49:51Z

wojciech-kulik
Nov 17, 2024
Maintainer

Hi,

Interesting case, the problem with using swift instead of xcodebuild is that it's missing things that the plugin requires to add some extra functionality.

For example, Test Explorer requires knowledge about tests received from logs, derived data, and xcresult file. Based on that all marks, diagnostics, code coverage, navigation to tests, and test tree are prepared. However, swift test doesn't provide most of those things. Not much more would have remained in general, in that case you could just bind swift test without all those integrations.

Regarding the build command, I would need to investigate that, because I'm not sure yet.

When working inside of Xcode I believe this is managed for you / new targets get added to the default -Package scheme, however when I'm working in nvim this doesn't occur

Hmm, I will check that, maybe it requires some flag or extra command.