All notable changes for this extension will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
- Command to generate a
compile_commands.jsonfile based on the current bazel workspace, the .bazelrc and extension settings.
- Some README adaptions.
- Use webpack to bundle extension.
- Log messages are now forwarded to extension output channel.
- Only touch 'external' paths in compile_commands.json with certain prefixes.
- Use progress notifications in addition to extension output
- Support official vscode testing API to discover, run, debug and anlyze
cc_testtargets via test explorer UI - Additional setting to switch on/off testing feature
- Additional setting to reduce the search space for large projects with many build targets
- compile_commands.json generation didn't work properly in case no symlinks for bazel-* directories were used
Explicitly assume that a cc_test label name matches the main cpp test file to overcome wrong associations in case of additional source files
clangd seems to have problems to resolve "isystem" added includes placed in the compile commands file, when using gcc to compile. A replacement with normal includes works.
- 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
- Add a QuickPick popup to support workspace selection on startup
- Use only selected workspace for test discovery
- Provide additional setting to specify bazel workspace directory
- Handle test definition across multiple lines properly
- 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