Proposed Task Api Feedback

[jrieken]

re #23280

• The TaskSet has two optional arrays allowing to list id of task that are test-tasks or build-tasks. While it's not entirely clear to me what that means it is somewhat cumbersome to repeat the ids there again, esp if I have created them programmatically. Chances are high I will add some sort of properly on my tasks for that and therefore I'd propose we make the API like that. Something like [ShellTask|ProcessTask]#kind which is an enum spelling out different task kinds
• Var-args like this constructor(name: string, commandLine: string, ...problemMatchers: ProblemMatcher[]); look nice but put in a corner wrt to evolving the API. You won't be able to add another parameter easily
• There is Task#identifier but there is no obvious reason why. It seems to be an internal property or does it surface in the UI in some form?

[dbaeumer]

I addressed the two first one. The identifier is basically optional but needed since I can't force UI names to be unique. If not provided then a task is using the name but when reference by another task there might be ambiguity. Then a user can add an identifier to make the fully unique. The tasks.json basically offers the same functionality.