Is there a way to get clangd to not abort when it encounters an unexpected .clang-tidy parameter? Same with clang-format and .clang-format? #117502
Description
Much like #111535, I was confused when an old project wasn't showing any linting results. I'm on clang 18.1.8 and couldn't tell you when I updated to that, but it was some time after the last time I looked at this project. Sure enough, it was because AnalyzeTemporaryDtors was in my .clang-tidy file. I deleted that, then I was off to the races!
However, I've had the same problem in reverse. I take a project I was working on with a relatively new clang version to a computer with an older clang version, and linting fails completely, because there is some .clang-tidy option or .clang-format option that the respective program freaks out about and bails.
So my question is this: instead of all of my projects breaking (with clang-tidy, clang-format, clangd, etc.) between versions of these programs... is there some way to tell these programs "If you run into a parameter you don't understand, just ignore it!" I know this probably shouldn't be default behavior, because if it silently ignores a check that the programmer is counting on, that could give a false negative. But this certainly seems appropriate for some sort of command line switch.
Hopefully, this is a feature that already exists and I've just missed it!
Lastly, I use Arch BTW and I'm programming in nvim