We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Doesn't matter.
Ability to use a dotenv file for test running. Exactly the same thing was implemented by the Go team here. Here's how it works:
"go.testEnvFile": "${workspaceFolder}/.env"
Then whenever you run a test it'll pick up the env vars from that file. Currently I do this workaround:
$ cd stream-chat-net $ export OMNISHARP_STREAM_API_KEY=xyz $ export OMNISHARP_STREAM_API_SECRET=xyz $ code .
With the OMNISHARP_ prefix it picks up the env vars but it's pretty inconvenient because I must start VS Code from the shell.
OMNISHARP_
A lot of us don't want to clutter our machine-level env vars but want to use "local" ones. This feature would make it possible.
The text was updated successfully, but these errors were encountered:
I guess I'll close it.
Sorry, something went wrong.
No branches or pull requests
Environment data
Doesn't matter.
OmniSharp log
Doesn't matter.
Feature request
Ability to use a dotenv file for test running. Exactly the same thing was implemented by the Go team here. Here's how it works:
Then whenever you run a test it'll pick up the env vars from that file. Currently I do this workaround:
With the
OMNISHARP_
prefix it picks up the env vars but it's pretty inconvenient because I must start VS Code from the shell.A lot of us don't want to clutter our machine-level env vars but want to use "local" ones. This feature would make it possible.
The text was updated successfully, but these errors were encountered: