Skip to content

Allow specific workspace folders to be referenced via ${workspaceFolder:folderName} #1774

Closed

Description

From Josh Cardenzana (@Jvinniec) in #1627 :
I'm trying to work in a workspace with multiple folders and according to this post I should be able to specify the paths to the individual folders with something like ${workspaceFolder:FolderName}. The relevant note is:

For example, in a multi root workspace with folders Server and Client, a ${workspaceFolder:Client} refers to the path of the Client root.

Activity

  1. azydevelopment commented on May 7, 2018

    @azydevelopment

    Is this due to get implemented? It would make development so much easier when you have a project that depends on another project but is in a different folder and want the includes to resolve correctly in the cpp properties json file.

  2. sean-mcmanus commented on May 7, 2018

    @sean-mcmanus
    ContributorAuthor

    azydevelopment It's not on our schedule yet, so I'm not sure when we'll get around to adding it...might just be a couple line change, not sure. I think it's possible to implement this in our open source code if anyone wants to contribute a fix :)

  3. bobbrow commented on May 22, 2018

    @bobbrow
    Contributor

    I opened a pull request for this.

  4. added
    fixedCheck the Milestone for the release in which the fix is or will be available.
    on May 22, 2018
  5. sean-mcmanus commented on May 22, 2018

    @sean-mcmanus
    ContributorAuthor

    azydevelopment It's implemented in 0.17.3.

  6. azydevelopment commented on May 23, 2018

    @azydevelopment

    Thanks guys that's awesome! I'll let you know if I run into any issues.

  7. locked and limited conversation to collaborators on Oct 14, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Feature RequestLanguage ServicefixedCheck the Milestone for the release in which the fix is or will be available.help wantedCan be fixed in the public (open source) repo.

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions