John Fairhurst

SourceKit has required an explicit SDK for CursorInfo for a few Swift releases now. So you need to include "-sdk", "/path/to/sdk" in the args. Yes, the error response from SourceKit...

The `structure` query just describes the parsed text of the program. You can use the SourceKit `cursor-info` request to get a type-checked view of an identifier -- `sourcekitten doc` does...

Latest SourceKitten is 0.34.1 -- 0.31.0 is three years old. The problem sounds familiar and I expect it is fixed in latest. If you do still see the problem on...

I don't know why the `@protocol` forward declaration prevents SourceKit from generating an interface for that declaration. The behaviour is the same in Xcode (counterparts -> Swift 5 interface) so...

You should check the rest of the log file: sourcekitten is saying that it doesn't contain a swiftc command to build the module `[ProjectName]Test`.

The build command `sourcekitten` is looking for starts with `/usr/bin/swiftc` and contains the flag `-module-name [ProjectName]Test`. Maybe check through the log and see what modules are being built?

That says `[ProjectName]Tests` but your CLI command says `[ProjectName]Test` (without the 's'). Is the typo in this GitHub issue or the actual problem? I'm only grasping at this nitpicky straw...

If that keeps happening after clearing up `.build`, `build`, and DerivedData for the project then I think that's as far as we can take it without a recreating project. This...

Quick workaround: temporarily replace line 1364 of that `debug.yaml` with ` "Generating XCTestCases":`. (And probably replace the module name in the command with `ValModule`). The error is because Yams is...

I can't think of a simple solution. To pursue the workaround above your process would be something like `swift build ; ; jazzy ` -- it looks like SPM won't...