Custom Variables Support In Workspace Settings

[angelhdzmultimedia]

Feature Request

Custom variables support in workspace settings.

Example

{
    "workbench.customVariables": {
        "themeColors": {
            "darkColor":  "#121212"
        }
    }

    "workbench.colorCustomizations": {
        "[Monokai Light Theme]": {
            "tab.activeBackground": "${themeColors.darkColor}"
        }
    }
}

[isidorn]

This is a feature request, but we do not have it on the current plan. Thus adding feature request and assigning to backlog.
fyi @alexr00 @aeschli

[wonson]

@isidorn Any updates?

Can the "inputs" in task.json apply in settings.json as well?

[isidorn]

No updates.
And no varaible substition is not supported in settings.json

[mingp]

This would be very useful for us as well.

As a different use case, our team wishes to check in a shared VS Code workspace config. We have a repo, whose structure is consistent, but which might be checked out at different locations by different team members. What we would like to be able to do is define a variable, in terms of e.g. ${fileDirname}, corresponding to the project root, and then define our other paths in terms of that. At present, we are having to repeat ${fileDirname}/../../<snip> everywhere.

[fquinsol]

This would be a really useful feature for the use case brought forward by @mingp .
The work around would be to relay on environment variables, but there is no way to provide default values that would work for most people in the team.

[alexchandel]

This would be extremely useful. Linting some projects requires providing absolute include paths (e.g. any modern Perl).

[gjsjohnmurray]

Related to #2809