CodecheckerVSCodePlugin icon indicating copy to clipboard operation
CodecheckerVSCodePlugin copied to clipboard

VSCode plugin that shows bugs detected by the Clang Static Analyzer and Clang Tidy analyzers using CodeChecker as a backend.

Results 24 CodecheckerVSCodePlugin issues
Sort by recently updated
recently updated
newest added

In the "results of the current file" tab, only the reports of the currently in focus file should be shown unless the report traverses multiple source files. Today it shows...

bug
LOW

Under the overview tab, add a CodeChecker settings link which takes the user to the Extention settings. This would be a convenience feature only, because the "extention settings" can be...

enhancement
LOW

I tried the VScode plugin with this setting: ``` json "codechecker.backend.outputFolder": "/tmp/${workspaceFolderBasename}/_build/.codechecker" ``` Turns out there is no "normal" variable expansion, like [described here](https://code.visualstudio.com/docs/editor/variables-reference). In combination with other plugins, full...

CodeChecker analysis can be slow (1-2 minutes). It would be good if we could show a pop-up window to inform the user when the analysis finished. We can show this...

enhancement
MEDIUM

In previous versions, the folder structure of .codechecker looked something like: ``` .codechecker - compile_commands.json - metadata.json - xyz.plist - ... ``` With CodeChecker 1.3.0 (commit 36448fb), the CodeChecker output...

More often than not only the last couple of steps are interesting in a bugreport - and maybe the very first step to see what was the first function under...

enhancement
LOW

Introduce a new configurable analysis timeout parameter (180seconds by default) for the analysis length of a single TU. It should be clear to the user, when this timeout happened what...

When I open a file, the "Reports in Current file" view should give me information about the current status of the analyis: 1) "Up-to-date" The reports are up to date...

Enabled analyzers, maybe enabled/disabled checkers, and other common flags should have their own separate option in the Settings menu. The commandline arguments should only be used as a last resort,...

We got an internal user report that the extension is incompatible with the Neovim vscode extension. Needs to be investigated more.