-
Notifications
You must be signed in to change notification settings - Fork 226
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support arbitrary sourcekit command? #312
Comments
Another possible solution to this problem would be for me to just use |
Even better I could use |
Great idea! As you mentioned, the |
I just submitted a slightly related PR which may or may not make sense to merge: #313 but this would allow consumers (possible for this usage) to pass yaml as well. |
nope, I think that's a great way to expose it |
Awesome! I think this is definitely a good start since this would also mean we wouldn't have to convert the jsonish representation, instead we could just pass the yaml right through |
While working on some editor integrations I found myself wanting to use sourcekit to get some info about my files/modules. To do this I was planning on passing some compiler arguments, along with some other info, to sourcekit for various requests that aren't particularly supported with a custom command in sourcekitten.
What do you all think about adding the ability in sourcekitten to execute arbitrary sourcekit requests, rather than the ones that are already supported with custom arguments in sourcekitten, so that you could pass something like:
through to sourcekit, without having to add a custom command in sourcekitten to handle this directly for every possible current, and future, sourcekit request. The benefit being you'd still be able to utilize the communication and parsing handled in sourcekitten, without having to have a command for each possible request.
The text was updated successfully, but these errors were encountered: