vscode-bazel
vscode-bazel copied to clipboard
Bazel support for Visual Studio Code
This is a feature request / idea. As documented [here](https://bazel.build/extending/config#using-build-setting-aliases), the `.bazelrc` file allows defining aliases for collections of command lines arguments to pass to the Bazel commands, like this:...
I have a repository using the bzlmod setup with Bazel 6. It doesn't seem like like the dependency resolution is working with MODULE.bazel usage.
Follow up to #309.
This change enables the target completion to work with 1) rules defined in external repositories: and 2) repository names: Depends on #306
Whenever I open buildifier in VSCode, I get a pop-up requiring me to download the buildifier setup for linting. However, when I download the amd-64 executable file and run it,...
Maybe this is expected behavior but I wanted to still check and confirm. Anytime I open a bzl file in a workspace within our repo which is a `local_repository`, it...
This commit teaches the LCOV parser to also read branch coverage data. Works towards #362
This commit adds demangling support for Java. I couldn't find any good third-party library for this, so I quickly implemented my own, based on https://docs.oracle.com/javase/specs/jvms/se8/html/jvms-4.html#jvms-4.3.2 It might still be have...
VS Code added support for code coverage recently (See https://github.com/microsoft/vscode/issues/123713). It probably makes sense to integrate this with `bazel coverage`, such that the code coverage is directly shown in the...
:robot: I have created a release *beep* *boop* --- ## [0.11.0](https://github.com/bazel-contrib/vscode-bazel/compare/0.10.0...v0.11.0) (2024-10-24) ### Features * Cmd-click to jump to a source file from a build rule ([#380](https://github.com/bazel-contrib/vscode-bazel/issues/380)) ([fa38d08](https://github.com/bazel-contrib/vscode-bazel/commit/fa38d08eceedf56777cfff2b8b0f74477e623154)) * **codelens:**...