consider to allow for variable substitution in the inputs section
See original GitHub issuetesting #64214:
I assume that variable substitution in the “inputs” section is disabled to avoid recursion…
However, I think it would be helpful to allow “simple” non-interactive variables like ${env:…}, ${config:…}, ${workspaceFolder:…}. This makes it possible to do something like this:
{
"label": "echoPrompt",
"description": "Please enter a folder name",
"default": "${env:HOME}",
"type": "prompt",
}
Issue Analytics
- State:
- Created 5 years ago
- Reactions:36
- Comments:9 (1 by maintainers)
Top Results From Across the Web
Predefined variable substitution in VSCode tasks user input
This issue suggests that variable substitution is currently not supported for inputs , but might be added sometime in the future: consider ...
Read more >Where variables can be used - GitLab Documentation
As it's described in the CI/CD variables documentation, you can define many different variables. Some of them can be used for all GitLab...
Read more >Variables reference - Visual Studio Code
Variables Reference. Visual Studio Code supports variable substitution in Debugging and Task configuration files as well as some select settings.
Read more >Variable substitution in the C shell - IBM
The C shell maintains a set of variables, each of which has as its value a list ... notations allow you to introduce...
Read more >6 Using Substitution Variables - Oracle Help Center
You can define a substitution variable of datatype NUMBER implicitly through the ACCEPT command. You will learn more about the ACCEPT command. To...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
My use case would be to use the path to the current file as the default value for one of my
inputs
.Are there any workarounds? i.e. any way to have a variable input default?