[suggestion] pass the arguments to the task for running task in parallel about undertaker HOT 6 CLOSED

Just pass the wanted array to Promise.map. It's not needed to come from the task.

var files = ['foo', 'bar', 'baz']
taker.task('processAll', function(cb){
  Promise.map(files, function(file){
    return take.task('processFile', file)
  }).nodeify(cb);
});

what's the case, exactly?

from undertaker.

@tunnckoCore : It's just a sample to describe the scene. And for your question, this means the task 'processAll' can not be reused to another place. But it's an user's choose, you can do such thing.

from undertaker.

Hm. Okey, then you can bind it to function.

var files = ['foo', 'bar', 'baz']
function processAll () {
  return Promise.map(this.files, function(file){
    return take.task('processFile', file)
  })
}
taker.task('processAll', processAll.bind({files: files}));
taker.task('all', processAll.bind({files: files}));

In one or another side, it would always come from somewhere, so that "somewhere place" would be the place to bind the context.

from undertaker.

Please do not abuse the binding.

from undertaker.

All of these examples are confusing and incorrect. If you want to reuse a "task" just make a module that is the function and require it in each place. The taker.task API you keep referencing doesn't do magic things like call your function, it just returns one to you or registers on in the system.

from undertaker.

Ok, that's all right If the undertaker just serve the 'src()' only. But this is not enough as a general task manager. I've implemented the Folder object in the custom-file to collect the files in the folder. It provides another way to process for gulp4 except src If undertaker can support it.

Anyway, very thanks the great gulp4 processor. I think it is the best practice of KISS. The gulp4 is a "nothing" processor. So I think undertaker should be one too. It's a little pity.

from undertaker.