Multiple targets at the end of the galvanize call are passed in reverse order

[MarcelloDiSimone]

The last changes that added chained target support, append the targets in reverse order to the galvanized grunt task. For example calling:

grunt.task.run(['galvanize:express:default:stop']);

calls the express task in this order:

express:stop:default

not as I would expect:

express:default:stop

I changed the handling of passed targets to keep the predefined order. I also rewrote the code to ES6 syntax and fixed the included mocha test, which didn't run the expectations but where still passing.

If for some reason the reverse handling of targets were intended, for some reason I don't know, please ignore the PR..

Cheers

[MarcelloDiSimone]

Are there any news about this change request or is the project dead?

[dylancwood]

Thanks for the bump. Will look at this PR today

On Tue, Jun 5, 2018 at 04:16 Marcello di Simone ***@***.***> wrote: Are there any news about this change request or is the project dead? — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#6 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AFCUwRP8HBF0_iVeZqjHbBB6blQg-TfHks5t5mh0gaJpZM4L1Z1Q> .

-- Cheers, Dylan 505 480 5346

…

--Sent from my Commodore 64 Desk Brick w/ Green Screen