By default clang-tidy will attempt to find the .clang-tidy file that is closest to the source file it is currently checking. This is useful if one wants to have different sets of checks for different folders. By setting --config-file explicitly this behavior is overriden, and all files are checked with the same config. It would be great if there was an option to disable the Python wrapper from passing the option at all!
By default clang-tidy will attempt to find the
.clang-tidy
file that is closest to the source file it is currently checking. This is useful if one wants to have different sets of checks for different folders. By setting--config-file
explicitly this behavior is overriden, and all files are checked with the same config. It would be great if there was an option to disable the Python wrapper from passing the option at all!