Daniel Krupp
Daniel Krupp
When a new source file is opened, the analysis (if not up-to-date) should be automatically executed in the background and the results shouldbe shown in the "reports in current file"...
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...
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...
In the VSCode plugin, in the “Reports in current file” view it is not possible to know if the analysis of a file was correct, failed and whether it is...
To get rid of the noisy checkers, the users wants to list the number of reports per checker and switch off the most noisy checkers. There is no convenient way...
When analyzing a large project, there are certain checkers which are very noisy producing ~10 000 reports. Then to get rid off the noisy checkers, there is a need to...
If the compilation action changes for a file in the compile commands.json (for example the cmake is reexecuted), new plist files will be generated for the same file. then the...
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...