Stop warning markers from polluting vscode minimap

clangd and other plugins tremendously increase efficiency when working with C++ in Visual Studio Code (vscode), but more plugins means more warnings and not everything is configurable. The above screenshot shows how a load of clang-tidy warning highlights from clangd clashes with the highlights for our search results in the minimap. This is going to slow down search-intensive tasks.

Ideally we fixed the warnings altogether or we adjusted the project’s clang-tidy settings so they won’t show up anymore. However, we all know these situations where we don’t have the time right now to deal with such things. So what else can we do? Disable warnings in clangd? Unfortunately that doesn’t seem possible:

To the rescue, there is a way to change highlight colors globally in vscode! So we can make warnings transparent in the minimap and in the overview-ruler:

{
  "workbench.colorCustomizations": {
    "minimap.warningHighlight": "#00000000",
    "editorOverviewRuler.warningForeground": "#00000000",
  },
}

Voilà!

We still see the warning squiggles in the editor, but they don’t pollute the minimap anymore.