Nathan Ridge

I think it would be valuable to document all refactorings / tweaks. Are you interested in writing a documentation patch?

> > Are you interested in writing a documentation patch? > > That will be fun. Thanks for your interest! > Can we collect a comprehensive list of refactoring support...

> Edit: please assign this issue to me. I don't have the permission to do that in this repository (it's not in the clangd org). Let's ask @kadircet.

> * Dump AST [since 9, [commit](https://reviews.llvm.org/rG395fde753c912e66964e1ce097f1ea6c59c79576)] This one is hidden. > * What is this "ObjCLocalizeStringLiteral"? [since 10, [commit](https://reviews.llvm.org/rG27f124445755a80e048a68d2fabbd2fa6f40a723)] It sounds like this is a tweak for wrapping an...

There are two more, [DefineInline](https://searchfox.org/llvm/rev/fa43608d1649553814a179cd76d67ea7bdc068d3/clang-tools-extra/clangd/refactor/tweaks/DefineInline.cpp#385) and [DefineOutline](https://searchfox.org/llvm/rev/fa43608d1649553814a179cd76d67ea7bdc068d3/clang-tools-extra/clangd/refactor/tweaks/DefineOutline.cpp#376).

> Is there any way we could get this more granular? For example, per file type? Note that you can already restrict settings to a file type, e.g.: ```json "[cpp]":...

To clarify, you have a single `compile_commands.json` file with multiple entries for the same source file?

Clangs does not currently have any way to control which of multiple entries for a given file in `compile_commands.json` is selected. There was one suggestion made in https://github.com/clangd/clangd/discussions/1288; please feel...

> A more automated solution I suppose would be to extend `compile_commands.json` format with config field (like [this](https://gitlab.kitware.com/cmake/cmake/-/issues/23450)) and additionally on the side of build system (cmake in this case)...

@thokra1 Does the recently fixed https://github.com/clangd/vscode-clangd/issues/48 address your use case?