CommandStack and ExecOneCommand cannot be used at the same time (since ExecOneCommand defines same property ($finishedAt)) about robo HOT 9 CLOSED

Oh... I closed referenced task before I implemented Timer :)

from robo.

Timer also does not need to be a trait actually.

You could simply use https://packagist.org/packages/phpunit/PHP-timer for example.

from robo.

I like traits a bit more than static calls.

from robo.

@boedah oh, why do you need ExecOne + Stack?

Stack is about running multiple commands one by one, ExecOne - to run exactly one command.
Actually I didn't think of combining them together...

from robo.

I think you still won't have a chance to include one into another because you still get conflicitng properties in this case :(

arg and option will append arguments to exact one command.
while Stack will ask for a set of different commands. Not sure how they are expected to run with same arguments. In your case you might think to define your own *Stack class.

from robo.

Btw, check latest update, I have removed some redundant methods from CommandStack

from robo.

Reason behind wanting to use both is: for Drush you can set global arguments which must not be set for each command (e.g. the drupal root directory and the site alias).

E.g.

$command = $this->taskDrushStack()
    ->drupalRootDirectory('/var/www/html/app')
    ->siteAlias('@qa')
    ->exec('command-1')
    ->exec('command-2')
    ->getCommand();

results in

drush @qa command-1 -y -r /var/www/html/app && drush @qa command-2 -y -r /var/www/html/app

I will make a PR with a suggestion to be able to do this.

from robo.

Thanks for explaining. I like your PR.

from robo.

I like traits a bit more than static calls.

But you can be in depencency hell...
A static Timer class can simply be used by any class who wants to use it...
Additionally, using e.g. PHP-timer would mean a little less NIH ;)

from robo.