Tony Allevato

Just to understand the specific problem, is this something that only happens once you open a BUILD file from outside the workspace—the diagnostics get added to the problems view and...

`BUILD` files should be recognized since they're listed in the package.json file here: https://github.com/bazelbuild/vscode-bazel/blob/master/package.json#L152 If you invoke the "Developer: Toggle Developer Tools" command, do you see anything in the console...

In the bottom-right area of the status bar, there should be a language identifier. Does it say "Starlark" or "Plain Text"? And if it's the latter, does changing it to...

Puzzling. I'm not sure what would cause your workspace to have a different configuration for those particular files, unless you had another extension installed that was colliding with ours, or...

@laurentlb, did you ever have any luck resolving this?

> Or is it better to ignore calls to `native.test_suite()`? E.g. if a function calls just this rule and no other rules (maybe transitively via other macros), it's ok that...

The crux of the issue here is that `-bundle` is set by Bazel (inside `AppleBinary.java`, based on the `binary_type` attribute) whereas the Bitcode flags are set via crosstool features, much...

@cpsauer Do you need to build any other macOS targets with Bitcode enabled? We recently added a platform-specific filter to `--apple_bitcode` so if not, you could use `--apple_bitcode=embedded --apple_bitcode=macos=none` to...

Indeed, the coverage support in the rules is currently for 🤫 internal use 🤫 at this time. I'm not too up-to-date on the current state of Bazel coverage. Bazel parses...

It looks like the version of `llvm-cov` distributed with Xcode 11 beta includes the `--format=lcov` flag that I added, so once that's in place, it would be up to the...