JP Simard

The way we do this for Swift is to run `xcodebuild` and parse the result for compiler arguments. Since SourceKit requires all the files to have been indexed, and the...

jazzy can be configured via a YAML file, and I would prefer if SourceKitten automatically detected Objective-C compiler arguments like we do for Swift, rendering that kind of error-prone &...

> Automagic is always best. Wish swift wasn't such a moving target. This is actually for Objective-C. We already do this for Swift and it's been quite stable!

See https://github.com/realm/jazzy#usage, https://github.com/bustoutsolutions/siesta/blob/master/.jazzy.yaml, https://github.com/danthorpe/Money/blob/development/.jazzy.yaml, https://github.com/natestedman/Shirley/blob/master/.jazzy.yaml, https://github.com/kaishin/gifu/blob/master/.jazzy.yaml, https://github.com/natestedman/Attributed/blob/master/.jazzy.yaml, https://github.com/DerLobi/Depressed/blob/develop/.jazzy.yaml

I don't think there's a way to drive SourceKit like this. Maybe you could ask in the swift-dev mailing list?

Yes, if you pass the swiftc compiler arguments to SourceKit and make a cursor info request for the location of the variable whose type you want, you'll get its inferred...

`sourcekitten docs` will get you that

`--single-file` expects that you're passing in the appropriate compiler arguments.

actually that's incorrect, it expects that that file is fully self contained.

Yeah, what you want is to get all the compiler arguments that would compile the module you're trying to mock. You can get this by doing a clean Xcode build...