v0.11.0

0.11.0 (2024-11-28)

Features

• Cmd-click to jump to a source file from a build rule (#380) (fa38d08)
• codelens: Add a copy target command (da62c67)
• codelens: Don't add target names for one line targets (#407) (4f02dc5)
• codelens: Extend CodeLens to build and run more targets (00d9971)
• coverage: Basic test coverage support (#366) (0d293b8)
• coverage: Demangling C++ & Rust function names in coverage results (#398) (d28c294)
• coverage: Demangling of Java function names in coverage results (#388) (7084368)
• coverage: Load branch coverage from coverage files #389 (e5c95e4)
• lsp: Add option to trace LSP communication (#425) (583fb65)
• syntax highlighting for .bazelrc (#379) (2aea27e), closes #259

Bug Fixes

• buildifier: Handle relative buildifier path without warning #387 (60051c5)
• Change explorer UI label to "Bazel Targets" (#409) (dba3102)
• codelens: Apply commandArgs to run targets (#408) (9c77c18)
• coverage: Do not emit error on BRDA:0 entries (#417) (7f62f0e)
• coverage: Expand external local repo in coverage report (#418) (c115a86)
• Default to Python syntax highlighting theme (#397) (2614f19)
• Link the full label / file name instead of individual components (#382) (2e207c9)

v0.10.0

0.10.0 (2024-04-09)

Features

• Add bazel.info.workspace command variable (#351) (8ae24cf)
• Add buildifier Json File Configuration (#357) (afc3aed)
• Introduce pickTarget and pickPackage command variables (#354) (2ef6d2a)
• Pick up .buildifier.json configuration from the Bazel workspace root (#350) (c2f3f8c)
• Support bazel tasks from tasks.json (#346) (f2426e4)
• Support relative paths for bazel.buildifierExecutable (#350) (c2f3f8c)
• Support running buildifier through Bazel (#350) (c2f3f8c)

Bug Fixes

• Activate the extension automatically (#344) (085262e)
• Add a welcome view to the Bazel Build Targets tree view (#372) (1cbdfd6)
• Don't wait on the "Buildifier not found" notification (#368) (8b659a2)
• Enable the "Restart LSP" command only if the language server is enabled (#345) (15793a4)
• Hide commands which are intended to be command variables (#347) (6d3e988)

Version 0.9.0 (February 20, 2024)

New Features

• Support relative target completion (@kon72)
• Add support for launching an LSP (@cameron-martin)

Bug fixes

• Make queries share the same server by default (@limdor)

Version 0.8.1 (January 2, 2024)

Bug Fixes

• Fix regressions caused by bazel query optimization in 0.8.0 (@daivinhtran)
• Add new and upcoming files names to the list of files marking the root of a repo / workspace (@hypdeb)

Internal Improvements

• Migrate to eslint (@hypdeb)
• Upgrade typescript (@cameron-martin)

Version 0.8.0 (December 15, 2023)

New Features

• Add codelens support for running binary targets (@avx-rchung)

• WORKSPACE.bazel is now identified as starlark (@lalten)

• Add bazel.runTarget command for running targets (@romannikov)

• Add bazel.queryOutputBase configuration setting (@sheldonneuberger-sc)

  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 a ramdisk for faster builds, or if your TMPDIR has space or security constraints.

• Add bazel.info.* commands (@jfirebaugh)

  This command can be used in launch configurations to embed the results of bazel info values. For example:

  "initCommands": [
    "platform settings -w ${command:bazel.info.execution_root}",
  ]
  

Bug Fixes

• Target completion no longer requires leading quotation mark (@kon72)
• Optimized performance of bazel query operations (@iamricard)
• CI updated to Node 20 (@jfirebaugh)

Version 0.7.0 (December 6, 2022)

New Features

• Add bazel.commandLine.queryExpression configuration setting (@maximMalofeev)

  A query language expression which determines the packages displayed in the workspace tree and quick picker. The default inspects the entire workspace, but you could narrow it. For example: //part/you/want/...:*

• Make executable and buildifierExecutable settings machine-overridable (@jfirebaugh)

  This allows them to be set in workspace or folder settings.

• Starlark syntax highlighting now applies to any file with a .bazel extension (@dierksen)

Bug Fixes

• Fix and document providing flags to getTargetOutput (@jfirebaugh)

  Additional Bazel flags can be provided to the bazel.getTargetOutput command:

  "inputs": [
      {
          "id": "debugOutputLocation",
          "type": "command",
          "command": "bazel.getTargetOutput",
          "args": ["//my/binary:target", ["--compilation_mode", "dbg"]],
      }
  ]
  

Version 0.6.0 (September 15, 2022)

New Features

• Add bazel.getTargetOutput command.

  This command can be used in launch configurations to obtain the path to an executable built by Bazel. For example, you can set the "program" attribute of a launch configuration to an input variable:

  "program": "${input:binaryOutputLocation}"
  

  Then define a command input variable:

  "inputs": [
      {
          "id": "binaryOutputLocation",
          "type": "command",
          "command": "bazel.getTargetOutput",
          "args": ["//my/binary:target"],
      }
  ]
  

Bug Fixes

• return default for .sky files in getBuildifierFileType (@arahatashun)

Version 0.5.0 (October 29, 2021)

New Features

• Implemented IntelliSense code completion for targets and packages in BUILD files.
• Added rudimentary goto definition handling for BUILD files.

Bug Fixes

• Fixed problems with CodeLens on Windows.
• Added support for "no-floating-promises" lint check and fixed violations.
• Made sure that multiple targets in CodeLens are sorted.

Contributors

We would like to thank Alex Frasson, Chi Wang, ericisko, hensom, Jonathan Dierksen and Neil Ding for their great contributions.

Version 0.4.1 (April 14, 2021)

Version 0.4.1 (April 14, 2021)

Bug Fixes

• Fix CVE-2021-22539: Malicious project can cause vscode-bazel to run arbitrary executable when linting a *.bzl file.

0.4.0 (August 21, 2020)

Version 0.4.0 (August 21, 2020)

New Features

• CodeLens has been disabled by default, but can be enabled via a new option.

Bug Fixes

• WORKSPACE.bazel files are now properly recognized.
• We made multiple improvements to Windows support.