Mismatch between tasks.json "type" default value from schema and reality

[Gama11]

Version: 1.42.1 (user setup)
Commit: c47d83b
Date: 2020-02-11T14:45:59.656Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Windows_NT x64 10.0.18363

(also tested with Insider's build b0be067)

---

According to the tasks.json schema / completion details, tasks use "type": "shell" by default:

To me this means that there should be no difference between having an explicit "type": "shell" and not having "type" specified at all.

---

In practice, this does not seem to be the case. To reproduce, create a tasks.json that looks like this:

{
	"version": "2.0.0",
	"tasks": [
		{
			"label": "test",
			"command": "test"
		}
	]
}

Also add this test.cmd file to your workspace root:

echo hello

It may be necessary to have "terminal.integrated.shell.windows": "cmd.exe" in the settings as well.

Running the test task results in this error:

> Executing task: <workspace-path>\test  <

The terminal shell path "<workspace-path>\test" does not exist

---

Now add an explicit "type": "shell" to the task - it now works as expected:

> Executing task: test <


<workspace-path>>echo hello 
hello

Conclusion: either the default value of "type" is not actually "shell", or something else is wrong.

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• User task description is wrongly shown with folder name (#89441)

[dbaeumer]

Verified that process is now the default value.