1.3.0
🔨 Improvements
- Better range positions for reports (#96)
If no range information is available for a report (for example in case ofclang-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 theCodeChecker log
command. It may also contain other files in the future. For this reason we changed the output folder of theCodeChecker 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.