Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

deno.path doesn't resolve environment variables #377

Open
Xernisfy opened this issue Mar 26, 2021 · 1 comment
Open

deno.path doesn't resolve environment variables #377

Xernisfy opened this issue Mar 26, 2021 · 1 comment
Labels
enhancement New feature or request upstream This feature requires upstream changes

Comments

@Xernisfy
Copy link

The setting "deno.path" doesn't seem to resolve environment variables.

In my settings.json I want to use an environment variable to resolve to deno.

Basically what I would like it to work with:
"deno.path": "${env:USERPROFILE}\\Applications\\deno\\deno.exe"
or
"deno.path": "%USERPROFILE%\\Applications\\deno\\deno.exe"

But it does work with an absolute path:
"deno.path": "C:\\Users\\<username>\\Applications\\deno\\deno.exe"

I tried this with the global settings.json and a workspace file.

Expected behavior

The environment variable should be resolved and enable the extension to find deno.

Screenshots

image

image

Versions

vscode: 1.54.3 (user setup)
deno: 1.8.2
extension: 3.2.0
os: Win10 build 19042

@kitsonk
Copy link
Contributor

kitsonk commented May 11, 2021

Currently vscode does not provide a service that does this (see: microsoft/vscode#2809) though I would really want something that is provided to extensions that would make this automatically work instead of trying to build it ourselves.

@bartlomieju bartlomieju added the upstream This feature requires upstream changes label Jul 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request upstream This feature requires upstream changes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants