[x] I have filed an issue about this change and discussed potential changes with the maintainers.
[x] I have received the approval from the maintainers to make this change.
[x] This is not a stylistic, refactoring, or cleanup change.
Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See
the Contributions section in the README for more
details.
Discussion thread for this change
Issue number: #6375
Description of this change
Since using clangd (-ibazel) to resolve virtual includes only works with the legacy engine and currently breaks it under some circumstances (see #6375) revert back to the old heuristics based approach by default. To enable the usage of clangd the bazel.sync.clangd.virtual.include registry flag can be set to true.
Checklist
Please note that the maintainers will not be reviewing this change until all checkboxes are ticked. See the Contributions section in the README for more details.
Discussion thread for this change
Issue number: #6375
Description of this change
Since using clangd (-ibazel) to resolve virtual includes only works with the legacy engine and currently breaks it under some circumstances (see #6375) revert back to the old heuristics based approach by default. To enable the usage of clangd the
bazel.sync.clangd.virtual.includeregistry flag can be set to true.