Using ${workspaceFolder} doesn't work for deno.path

[zephraph]

@hverlin, love the extension! Thanks for all your work.

I have a PR that enabled symlinks on one of my repos but when I was testing it deno kept failing to find the binary. I thought, at first, that deno just wasn't playing well with symlinks. It turns out that vscode just doesn't do automatic variable substitution in config strings. This will be a problem for other extensions that haven't implemented a solution for ${workspacePath} replacement.

I upstreamed a PR to fix this (denoland/vscode_deno#1245), but for now folks will likely have to add deno to the automatic ignore list.

[hverlin]

Thank you for the bug report. Indeed, I can reproduce the issue, sorry about this.

I have also tried to set to a relative path like @syhol did here: https://github.com/syhol/mise-vscode/blob/main/src/extension.ts#L222 (i.e. to "deno.path": ".vscode/mise-tools/deno") and it does not seem to work 😞

It appears that even not all built-in VS Code settings support variable substitution, according to https://code.visualstudio.com/docs/editor/variables-reference#_is-variable-substitution-supported-in-user-and-workspace-settings

I will disable this feature for the deno extension (so it will use the absolute path instead) and will review the other extensions to make sure they work. Likewise, I know that a few other extensions like php or flutter do not play well with symlinks.

[zephraph]

Unfortunately my upstream PR was rejected so I don't think this'll be fixed.

[zephraph]

I just wanted to update folks on the solution I found to help with this: zephraph/webview#125.

Essentially I'm using https://github.com/swellaby/vscode-workspace-config-plus to make sharable configs and .gitignoring the main settings.json. Hopefully that helps anyone else who runs into this.