Multi-Root task provider (Add root-directory and workspace-name properties to Task)

[elahehrashedi]

This issue is related to task provider behaviour in a multi-root workspace set up.
Consider this multi-root workspace:

and let's say I want to configure a new task for a .cpp file in Root3. This is what I get by running "Configure Task" (the other root's tasks will be shown as well).

A similar issue arises when trying to set a default task in Root3. there can be other defaults in every root. but the default is picked from root1.

@alexr00 I know you are tracking this issue already. Just for having it all in one place, I put the related issues here:
#111037
#99276 (possibly showing the tasks for the working directory on the top of the list of the tasks, e.g. #89448).
#35312

The same issue may need to be resolved if multiple workspaces is going to be supported:
#43188

[vscodebot]

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

• Provide Task Runner viewlet (#28235)
• Ordering and naming tasks (#89448)
• Run Task or Build Task without open workspace (#118370)
• Executing terminal > run task two times will not terminate the original task when restart is selected (#118963)
• Task started with vscode.tasks.executeTask doesn't generate any completition notification if dependency task fails, preventing its execution. (#97475)

[alexr00]

@elahehrashedi you can provide a WorkspaceFolder as the Task scope. Does that solve this for you?

vscode/src/vs/vscode.d.ts

Lines 6576 to 6577 in 02d3809

	constructor(taskDefinition: TaskDefinition, scope: WorkspaceFolder | TaskScope.Global | TaskScope.Workspace, name: string, source: string, execution?: ProcessExecution | ShellExecution | CustomExecution, problemMatchers?: string | string[]);

[elahehrashedi]

@alexr00 kindly, no, that doesn't solve the issue. I have tried both WorkspaceFolder and TaskScope.Workspace.
It partially solves the problem for "Configure Task". but not the "Configure default build task" (It only works if the previous folders don't include a tasks.json file, and don't have a default already)
I have a question as well, were WorkspaceFolder and TaskScope.Workspace added to solve this issue? What is the expected behaviour for each of these scopes?

[elahehrashedi]

@alexr00 I modified the report above to show the results when using WorkspaceFolder instead of TaskScope.Workspace.
The problem is still unresolved. :)

[alexr00]

let's say I want to configure a new task for a .cpp file in Root3. This is what I get by running "Configure Task" (the other root's tasks will be shown as well).

It is expect that we show all tasks from all sources when you run "Configure Task". I think this is the correct behavior, though the grouping/sorting could be improved as said in the issue linked (#89448).

The issue you show with default build task is definitely a deficiency. Tracked by #35312, which I will investigate fixing for the June release. Thank you @elahehrashedi for bringing it to my attention!