-
Notifications
You must be signed in to change notification settings - Fork 13
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
Environment variable substitution doesn't work in settings.json #592
Comments
It cannot be guaranteed so it may well not be, see also #109 which is mainly about getting it to run as early as possible. People have also shared a workaround there which I think was to open a different kind of file first, like markdown, so the go extension would run later? That said I would have assumed that vscode resolves the settings before loading any extensions, in which case your snippet would actively prevent this extension from affecting the go extension. |
Sorry, I missed replying to this. I'm not exactly sure how to check this. What I did currently was to look at the Output from extension host is as below:
|
I have a vscode workspace with the workspace settings as follows:
direnv extension logs picks up the value correctly but the Go extension complains saying that
${env:GOROOT}
is not a valid goroot.Is direnv the first extension to start or can that be guaranteed in any way so that the environment variables are loaded before any other extension?
The text was updated successfully, but these errors were encountered: