Steps to reproduce:
- Create a tasks.json under a .theia folder
- Add a task which takes in an input, for example, the file I reproduced the bug with is:
- Run the task via the command palette
- When prompted to enter the input, click away, anywhere on the screen
What happens:
The task gets run with no input passed in.
Expected behavior:
Not sure if this is supposed to be the expected behavior, but I feel like the behavior which VS Code has is more intuitive. Nothing happens unless the user either presses Enter or Escape. Clicking away does not trigger the task.
Additional information:
- Operating System: Windows 11
- Theia Version: 1.73.100
Steps to reproduce:
{ // See https://go.microsoft.com/fwlink/?LinkId=733558 // for the documentation about the tasks.json format "version": "2.0.0", "tasks": [ { "label": "echo", "type": "shell", "command": "echo Hello ${input:programmer_id}" } ], "inputs": [ { "id": "programmer_id", "type": "promptString", "description": "FlashPro programmer serial number (e.g. S2011JOH9N). If unsure, run ${PFSDK_ROOT}/modules/debug/fpserver/run_fpserver.sh (or .cmd for Windows) --list" } ] }What happens:
The task gets run with no input passed in.
Expected behavior:
Not sure if this is supposed to be the expected behavior, but I feel like the behavior which VS Code has is more intuitive. Nothing happens unless the user either presses Enter or Escape. Clicking away does not trigger the task.
Additional information: