microsoft / microsoft/vscode-makefile-tools

Variable expansion in multi-root workspaces

Open

#467 opened on May 1, 2023 2 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement Feature: multi-root Feature: variable expansion

Dominant language: TypeScript
Stars: 242
Forks: 78
PR merge metrics: No merged PRs in 30d

Description

Makefile Tools version: 0.7.0
VSCode version: 1.77.3

In a multi-root workspace `${workspaceFolder:[name]} should expand to the workspace path called out by [name].

Example workspace:

{
    "folders" [
        {
            "name":  "App",
            "path":  "C:/Projects/LED_blink"
        },
        {
            "name":  "SDK",
            "path":  "C:/SDKs/SomeSDK"
        },
    ]
}

Variable	Expected Expansion	Actual Expansion
`${workspaceFolder}`	`C:/Projects/LED_blink`	`C:/Projects/LED_blink`
`${workspaceFolder:App}`	`C:/Projects/LED_blink`	`C:/Projects/LED_blink/unknown`
`${workspaceFolder:SDK}`	`C:/SDKs/SomeSDK`	`C:/Projects/LED_blink/unknown`

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Research direction

Reproduce the report using the multi-root workspace example and the listed ${workspaceFolder} variables in VS Code. Trace the Makefile Tools workspace-variable expansion path; done means ${workspaceFolder:App} and ${workspaceFolder:SDK} resolve to their named folder paths instead of an unknown subpath.

Written by the indexing model from the issue text.

Assessment

Tech stack: typescript, vscode
Domain: developer-experience, tooling
Issue type: Bug
Difficulty: 3/5
Estimated time: 1-2 days
Activity status: Stale
Clarity: Mostly clear
Newbie friendliness: 45/100

A short digest of beginner-friendly GitHub issues.