Currently Clang tidy provider searches from the root directory up to the target directory, this is the opposite of how clang-tidy searches for config files.
The result of this is .clang-tidy files are ignored in any subdirectory of a directory containing a .clang-tidy file.
Details
Details
Diff Detail
Diff Detail
- Repository
- rG LLVM Github Monorepo
Event Timeline
Comment Actions
I have made an extra test case that compares the output of our provider to the output of a clang::tidy::FileOptionsProvider, This would ensure coherent behaviour between our implementation and clang-tidy implementation.
However I'm not sure it should be included as any changes made on the clang tidy side may break that test and we shouldn't be enforcing clang-tidy maintainers to also ensure compliance with clangd.
Comment Actions
Sorry about dropping this (and others, i'm trying to get through them now)
Agree about cherrypicking this.
Regarding the extra test case... I'm not sure either. It's a nice test, but the conceptual dependency is annoying.
If it's simple enough, feel free to add it and we can remove if it causes problems.