search

alefragnani / vscode-project-manager

Project Manager Extension for Visual Studio Code
GNU General Public License v3.0
1.94k stars 223 forks source link

[BUG] - Windows Environment Variables doesn't work #584

Closed Konstantine-Nevzhunskyi closed 2 years ago

Konstantine-Nevzhunskyi commented 2 years ago

Providing rootPath in projects.json with some Environment Variable doesn't work.

Steps to reproduce

  1. Set rootPath like "rootPath": "%GD_Path%\\test"
  2. Try to open project.
  3. Get error "Path does not exist: The path '\%GD_Path%\test' does not exist on this computer."
alefragnani commented 2 years ago

Hi @Konstantine-Nevzhunskyi ,

The extension does not support environment variable. You can, however, use ~ or $home as a replacement for your home folder.

There is an open issue (#550) requesting to add support for other/environment variables. Feel free to add new comments and upvote the issue, so I’m able to track user feedback.

Hope this helps

Konstantine-Nevzhunskyi commented 2 years ago

Sorry, I just thouhgt that it is bug, coz I just tried to use usual path for my system. In issue #550 talks about more powerfull functionality with some parsing/replacement in pathes. So I decided that there is some bug (for example some path transformation regardless of the fact that there are pathes in Windows that starts with "%"), as I know there is no need in additional code to make this pathes right handled by system.

alefragnani commented 2 years ago

No problem. #550 idea will be to support environment variables, probably similar to what VS Code does.