1.6.0

🔨 Improvements

• CodeChecker detailed status on the sidebar in #146
  Displays a more detailed description of the status of CodeChecker runs, including warnings and errors encountered.
  
• Analyzers now run in "lean" mode by default in #152
  The default flags for CodeChecker and the Clang Static Analyzer were changed, so it runs in a shallow mode by default, and it does not consume all system threads. This helps ensure that the development environment remains usable while a background analysis is running.
• Analysis timeout parameter in #154
  Added a default timeout of 60 seconds for each individual analysis that CodeChecker runs. Longer-running and stuck analyses are terminated after the timeout, letting the CodeChecker run progress.
• Option to change how severities are displayed in #141
  The new settings allow choosing between warning/error/note display styles for each CodeChecker report severity.

🐛 Bug fixes

• Fix codechecker.executor.showOutput command in #144

(There were some hiccups with the release automation, that is why the release showed up multiple times in the notifications.)

1.5.1

🔨 Improvements

• Rework UI to handle CodeChecker's autodetection by @Discookie in #130

1.5.0

🔨 Improvements

• Initial multi-root support in #121
  Adds support for CodeChecker 6.22's automatic compilation database detection. If no compilation database is specified, and there is none in CodeChecker's output folder, the extension will use CodeChecker's autodetection (for 6.22 and above). For 6.21, and the mentioned cases, the behaviour remains the same.
• Notifications overhaul in #116
  Added a sidebar view to show past notifications. The notifications actions can still be executed through the sidebar, even if the user disabled pop-up notifications.
• Notifications for the executed processes in #120
  Added notifications for adding CodeChecker log and analyze commands to the queue, and then executing them.
  They are mainly displayed on the sidebar, and there are actions for killing the process or removing them from the queue.

🐛 Bug fixes

• Migrate to Yarn 2+ and bump dependencies in #123
• Fix build command argument for CodeChecker log in #124
• Extend timeout for file watcher events in #125

1.4.0

🔨 Improvements

• Refactor report tree (#112)
  Refactor the report tree's code.
  Display depth of report steps.
  Group reports by severity levels.
• Add Go to docs button to sidebar (#109)
  The documentation URLs are fetched by running CodeChecker checkers at project load.
  
• Add architecture.md (#105)
  Adapted from my private notes with minimal changes, but should be fine for this purpose.
  The image can be edited via https://draw.io/.
• Integrate CodeChecker log into executor (#108)
  Fixes (#38).
  Instead of running CodeChecker log as a separate process, it is now integrated into the `backend/executor.
  
  Added commands, build tasks, UI buttons for running CodeChecker log.
  Added settings to specify custom args as well as a build command, which can be overridden by commands or tasks.
  Added a couple tests for the backend.

🐛 Bug fixes

• Improvements for handling CodeChecker version checks (#114)
• Fix handling of removed processes from the execution queue (#110)
• Refactor keyboard navigation (#106)

For more information check the milestone.

1.3.0

🔨 Improvements

• Better range positions for reports (#96)
  If no range information is available for a report (for example in case of clang-tidy) we will use the VSCode API to get word position at the given line + column position and use it to highlight the location of the report.
• Hide codelens and bug step decorations when document is dirty (#93)
  If there are unpersisted changes in the current document we will hide the provided codelens items and bug step decorations.
• Deduplicate scheduled tasks based on command line (#95)
  If the same file is being saved multiple times while the analysis is ongoing, do not add the re-analysis of the same file multiple times to the analysis queue, because it is superflous.
• Change CodeChecker analysis output to .codechecker/reports (#91)
  .codechecker directory may contain compilation database which is generated by the CodeChecker log command. It may also contain other files in the future. For this reason we changed the output folder of the CodeChecker analyze command to .codechecker/reports.
• Highlight bug step ranges when a bug is selected (#88)

🐛 Bug fixes

• Refactor executor to pass shell arguments as array (#57)
• Change value of version process type to analyzer-version (#97)
• Expand user in the CodeChecker binary path (#98)

For more information check the milestone.

1.2.0

🔨 Improvements

• Show checker name in the bug tree for each report (#68)
• Add icons to the statusbar text (#67)
• Change required VSCode API version to 1.53.0 which is supported by the latest Theia editor (#83)
• Extend the help of the analyzer arguments configuration option (#82)
• Rename Database path to Compilation Database Path (#81)

🐛 Bug fixes

• Fix showing diagnostics in the Problems pane (#70)
• Check supported CodeChecker version when the CodeChecker executable path configuration setting is changed (#69)
• Fix showing output channel in Theia editor (#84)
• Fix keyboard navigation commands (#75)

For more information check the milestone.

1.1.0

🔨 Improvements

• Find compilation database automatically in the project (#52)
  The extension will try to find compilation databases (compile_commands.json, compile_cmd.json) automatically in the following directories:
  • $WORKSPACE_DIR/.codechecker
  • $WORKSPACE_DIR
  • $WORKSPACE_DIR/build
• Keep active repr. steps open when switching files (#60)
  If we click on a report step which refers to a different source file (e.g.: lib.h) than the currently opened file (e.g.: main.cpp), the plugin will show the reports from that file but will keep the selected report in the bug tree.
• Remove unclosable CodeChecker analysis in progress window (#64)
  On large projects the analysis may take huge amount of times (e.g.: minutes). In this case it is really annyoing for the user to show an unclosable pop-window. Also this information whether an analysis is running already available in the bottom bar. For this reason we removed this pop-up window but introduced a new tree item on the overview sidebar to stop the analysis.

🐛 Bug fixes

• Set priority order for settings items (#55).
• Wait for terminal initialization for CodeChecker log command (#54).
• Reduce number of parse calls (#58).
• Fix adding selectedEntry to openedFiles (#63).
• Use matrix strategy at deploy github action (#48).
• Remove fast-plist dependency (#53).

For more information check the milestone.

1.0.0

🎉 CodeChecker VSCode plugin

Today we are proud to announce the first official release of CodeChecker VSCode plugin.

🌟 Main features

• Run CodeChecker analysis from the editor and see the results automatically.
• Re-analyze the current file when saved.
• Commands and build tasks for running CodeChecker as part of a build system.
• Browse through the found reports and show the reproduction steps directly in the code.
• Navigate between the reproduction steps.

💻 Trying It Out

1. Install CodeChecker version 6.18.2 or later and optionally add it to the PATH environment variable.
2. Install CodeChecker extension from the Visual Studio Marketplace, from Open VSX or download manually from Downloads.
3. Check the path to CodeChecker and set your preferred command-line arguments - see Configuring CodeChecker for more information.
4. Open your project, and run an analysis, or browse through the found reports!

For more information about this release see the milestone.