v0.6.7

Fixed

• Fix freeze of compile commands generation in case of non-existing compile_commands.json file
• Prevent extension startup error in case of user cancelation of workspace selection

v0.6.6

Fixed

• Handle test definition across multiple lines properly

v0.6.5

Added

• Provide additional setting to specify bazel workspace directory

v0.6.4

Fixed

• Use only selected workspace for test discovery
• Prevent stopped test discovery in case of unrecognizable src files

v0.6.3

Fixed

• Harmonized test file paths to avoid duplicate entries in Test Explorer UI
• Switched to stream handling for file manipulation to prevent errors in case of large compile_commands.json files

Added

• Add a QuickPick popup to support workspace selection on startup

v0.6.2

[0.6.2] 2023-12-05

Fixed

clangd seems to have problems to find "isystem" added includes placed in the compile commands file, when using gcc to compile. A replacement with normal includes resolves the problem.

v0.6.1

Fixed

• Explicitly assume that a cc_test label name matches the according main test cpp file to overcome wrong associations in case of additional source files.

v0.6.0

Added

• Support official vscode testing API to discover, run, debug and anlyze cc_test targets via test explorer UI
• Additional setting to switch on/off testing feature
• Additional setting to reduce the search space for test discovery via target label

Fixed

• compile_commands.json generation didn't work properly in case of no symlinks for bazel-* directories were present

v0.5.0

Added

• Use progress notifications in addition to extension output

v0.4.0

Added

• Log messages are now forwarded to extension output channel.

Fixed

• Only touch 'external' paths in compile_commands.json with certain prefixes.