Add a rerun last task command

[alexr00]

Fixes #25310

[dbaeumer]

Can you quickly explain why we need this?

[alexr00]

In handleExecuteResult in task.contribution.ts we need the Task that was executed. For tasks that were run using rerun, task.contribution.ts has no knowledge of the task. Putting the task in the execute result solves this.

[dbaeumer]

LGTM. Only one questions.

With these changes you will own the terminal task system :-)

[dbaeumer]

Actually there is on thing we should think about: would it make sense to let users control what rerunning means in a per task basis. I could for example imagine that rerunning some tasks should reevaluate the vars and rerunning some other should not. So would be cool if I can control this with a property on the task itself. The question will then be what the default is. I would actually argue to should rerun and reevaluate.

[alexr00]

As a task property, I agree that the default should be to rerun and reevaluate. Having the task revaluate seems like a logical step from Run to Rerun, while having it as a setting gives the user more power to use the already evaluated variables. I'll make this change.

[dbaeumer]

Would it make sense to introduce a RunOption and have a property in there and move the isBackground there as well. I am indifferent as well but top level things on the task might get messy at some time.

[hendrics]

@alexr00 this is a long awaited feature! Thank you for this!

One quick question though - there are no tests for this feature except adding a custom section, or does it do more?

[alexr00]

I didn't write any new tests for this command, that's correct. You do not need to add anything to your tasks.json to try it out with the default rerun behavior. The default behavior is that all task related variables will be re-evaluated. If you want to make your task run faster and you always want the same variables as the previous run, you can set the runOptions in your tasks.json to have "rerunBehavior":"useEvaluated"

[hendrics]

I am looking forward to trying it when it’s released! I am just curious it was accepted with no automated tests. I am wondering if it is a newer tendency and automated tests no longer considered a best practice?
Nevertheless thank you for implementing it! I am just concerned this or other functionality might regress. And I use vscode everyday :-)!