You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
For my team we have multiple repository that contain code that needs to be able to be debugged in the same "shell env".
To this end we have setup the desired environment in a seperate repository.
We would like the VSCODE extension to be able to specify a default devbox.json file to open, as fallback for when there is not a more specific devbox.json in the repository.
Would this be possible?
What solution would you like?
Add an option for default devbox.json file specification in extension config params:
Alternatives you've considered
Allow users to give command line params to the devbox shell command being called from the visual studio code extension (like --config).
The text was updated successfully, but these errors were encountered:
What problem are you trying to solve?
For my team we have multiple repository that contain code that needs to be able to be debugged in the same "shell env".
To this end we have setup the desired environment in a seperate repository.
We would like the VSCODE extension to be able to specify a default devbox.json file to open, as fallback for when there is not a more specific devbox.json in the repository.
Would this be possible?
What solution would you like?
Add an option for default devbox.json file specification in extension config params:
Alternatives you've considered
Allow users to give command line params to the devbox shell command being called from the visual studio code extension (like --config).
The text was updated successfully, but these errors were encountered: