Thomas Van Lenten

Depending on what you find, it might make sense to open up an issue on bazel itself with your details and reference some of the docs referenced here because either...

The code tries to handle this already, for the 0.1.0 release it should be hitting: http://go/gh/bazelbuild/vscode-bazel/blob/0.1.0/src/bazel/bazel_command.ts#L96 Can you trace through there, what are you getting back that the check for...

Are you on windows?

Then #153 was likely the same issue. It should be fixed on master, but a release hasn't been done yet.

Maybe not #153 directly, but #158 in general might have gotten things.

The first seems to have gone away, I did a quick attempt at the second with: ```patch diff --git a/src/extension/extension.ts b/src/extension/extension.ts index 9d87e79..29745a5 100644 --- a/src/extension/extension.ts +++ b/src/extension/extension.ts @@ -82,26...

For clarity, what do you mean by _external repository files_? Do you mean things not under the folder(s) that VSCode was opened on? Do you mean things not in the...

To collect the packages we do `bazel query '...:*' --output=package`. Looking closely, if one is at the root of the repo, the output include a blank line (as that package...

If the vscode workspace root is a sub package, then the query does pull up the package just fine, so the question really is how do we want to show...

To clarify, this issues isn't just with Swift, the question is a general question about how to handle enums evolving and the json encoding.