Included VS Code Configuration Does Not Use `compile_commands.json`

Hi all,

I’m wondering why the included VS Code configuration in the main source tree does not just use the compile_commands.json that is automatically generated during each build and placed in the build directory. I’ve read in the documentation that supposedly the development environment setup is really easy with VS Code and only takes several minutes, but that isn’t the case for me. I get lots of incorrect errors and the editor can’t find any of the required files/includes. When I remove most of the manual configuration in .vscode/c_cpp_properties.json and just point it to one of the generated compile_commands.json files, everything works fine.

Is there a reason the project doesn’t just do that instead?

My current configuration which works well

{
    "configurations": [
        {
            "name": "PX4",
            "configurationProvider": "ms-vscode.cmake-tools",
            "cppStandard": "c++14",
            "cStandard": "c11",
            "compileCommands": "build/cubepilot_cubeorangeplus_default/compile_commands.json"
        }
    ],
    "version": 4
}

The official configuration

{
    "configurations": [
        {
            "name": "PX4",
            "includePath": [
                "${workspaceFolder}/**",
            ],
            "defines": [],
            "macFrameworkPath": [],
            "configurationProvider": "ms-vscode.cmake-tools",
            "cppStandard": "c++14",
            "cStandard": "c11",
            "forcedInclude": [
                 "@PX4_BINARY_DIR@/px4_boardconfig.h",
                 "@PX4_SOURCE_DIR@/platforms/common/include/px4_platform_common/defines.h"
                 ]
        }
    ],
    "version": 4
}