vscode-bazel
vscode-bazel copied to clipboard
Bazel support for Visual Studio Code
Currently "Build/Test Target" commands only work from bazel target panel, and that panel is not very useful when there are hundreds of targets (eg. in a monolithic repo). Any attempt...
Add debug logs throughout major functions in this extension reporting the elapsed time in the function to help debug issues like #60 and #58
Many times, BUILD files contain macros that generate targets that are purely implementation details that are meant to be hidden from the user (for example, `ios_application` currently produces a handful...
I have a macro that creates a lot of targets and they end up going outside the screen, see:  To be fair we can probably could make the macro...
We currently have no tests for the extension. VS Code extension testing framework described here https://code.visualstudio.com/docs/extensions/testing-extensions We will need to add a starter test and include it in the PR...
(From #17) We should leverage Bazel's [Build Event Protocol](https://docs.bazel.build/versions/master/build-event-protocol.html) in the extension so that we can provide various UI feedback about builds the user launches, such as (just some random...
The plugin gives an error in a basic empty project. This popup opens when you expand the "Bazel build targets"  (All the folders are empty at this point)
I am able to build projects using this extension, but I have not been able to get VS Code to resolve external dependencies using anything that I can find in...
Adds an outputBase string configuration that changes where output_base is placed. This is convenient for when someone wants bazel using something other than TMPDIR. This is useful if you use...
This commit introduces the `bazel.pickTarget` and `bazel.pickPackage` command variables. Those commands can be used from `tasks.json` and `launch.json` to prompt the user to select a Bazel target or package. The...