Overriding included tasks

[samegutt]

Given the two scripts CommonTasks.ps1

Task Build -depends Clean, Compile

Task Clean{ }

Task Compile { }

and MyTasks.ps1

Include ".\CommonTasks.ps1"

task default -depends Build

task MyClean -alias "Clean" { }

The task MyClean effectively overrides the task Clean with its alias, giving the following output:

C:\> Invoke-psake .\MyTasks.ps1
Executing MyClean
Executing Compile

Build Succeeded!

Q: It this by design? Or is this unintentional? I am creating some common build steps for the project I work for, and some of the modules needs some customisation to the build flow. Using the -alias parameter I get the functionality I need, but the solution has some apparent smells.

Suggestion: An -override parameter would make the purpose of MyCleanvery clear.

[UberDoodles]

@samegutt

I just posted a reply to #298, and I realised my reply might also apply here. Interestingly, that issue suggested the ability to merge tasks, rather than override them.

Generally, I don't define dependencies for any tasks which have an action. When I want to chain tasks together; I create a separate task for that purpose. It gives you more flexibility to run exactly what you want to.

Would that help you achieve what you are trying to do?

There might be other use cases where being able to override (or merge) tasks is useful though, and I like your suggestion about adding an -override parameter to make it clear what is going to happen to the two task definitions.