dopplerhq / vscode Goto Github PK

Thanks for this extension, looks great! My company uses a (turborepo) monorepo, and so there are separate projects that use different Doppler projects by directory. We have different doppler.yaml files in each of those folders to declare the proper project/environment for local dev.

Would be pretty sweet if we could at the minimum configure different configs for different subdirectories, or even better just have Doppler look for doppler.yaml files and figure it out itself. Also, the extension prompted me to select the proper project and env, but no idea where that's stored, I thought it would be in settings.json but i guess not.

So yeah really a few ideas in this issue, but for now the main thing that would block me from making effective use of this is multiple projects in my workspace. Thanks!

Hi,
I have not been able to get this extension working on VSCode windows. Is it supported?
Installed doppler with scoop. Tried login and setup, installing and uninstalling the extension in various combinations. When I`m in a project-folder, the extension is simply in a "waiting/hanging" state.

In our development container, we manually configure Doppler by setting the environment variable DOPPLER_CONFIG_DIR. This causes the valueFromEnvironmentNotice CLI function to be called each time a Doppler command is executed.

(Note: this can be irritating when executing doppler run frequently. It would be ideal if this warning could be disabled or only output once per day/session. A separate issue has been opened for this: DopplerHQ/cli#407)

Whenever valueFromEnvironmentNotice is called, it writes a warning to stderr, which opens the VSCode Output panel and moves the user's cursor and focus to that panel. For those using environment variables to configure Doppler, this behavior makes the extension impossible to use.

I recognize the importance of providing error feedback to the user, however, I am not aware of any other VSCode extension that takes control of the user focus in this manner.

I am happy to submit a pull request for this. This can be fixed simply by removing line 97.