Today it is disturbing that codechecker analysis is activated also on file changes that are not C/C++ files, while it currently only supports the analysis of C/C++ files.
The following improvements could be implemented:
- Add a new configuration option to the vscode plugin:
extension_filter This should contain a list of file extensions to which CodeChecker analyze is invoked. By default it should have the following value: ".c, .cc, cpp, .cxx"
CodeChecker analyze should not be invoked on any other files.
What should happen if no source file is in the project which matches the "extension_filter":
-
If a project is opened which does not contain at least one C/C++ file (file matching the extension_filter) don't display any notifications about missing compilation database (as is done currently)
-
the projects the sidebar overview should display "CodeChecker only supports analyzing <extension_filter> files"
-
for changes on unsupported files, the CodeChecker analysis should not be executed at all. Today, it runs on all file save
Today it is disturbing that codechecker analysis is activated also on file changes that are not C/C++ files, while it currently only supports the analysis of C/C++ files.
The following improvements could be implemented:
extension_filterThis should contain a list of file extensions to which CodeChecker analyze is invoked. By default it should have the following value: ".c, .cc, cpp, .cxx"CodeChecker analyze should not be invoked on any other files.
What should happen if no source file is in the project which matches the "extension_filter":
If a project is opened which does not contain at least one C/C++ file (file matching the extension_filter) don't display any notifications about missing compilation database (as is done currently)
the projects the sidebar overview should display "CodeChecker only supports analyzing <extension_filter> files"
for changes on unsupported files, the CodeChecker analysis should not be executed at all. Today, it runs on all file save