Add handler flow control option.

[anseki]

Add handler flow control option.

[anseki]

Thank you for your post.

Sorry, but I can't understand "task handler" and "target handler".
Is "task handler" "handlerByTask" ? and is "target handler" "handlerByFile"?
If handlerByTask returns false, exit current task immediately, and the remaining handlers are not called. If it returns true, the remaining handlers are called.

If you mean Targets in Configuration, you can control it via specifying like grunt task1:target1 or grunt task1.

[6aKa]

"task handler" - handler which defined in task option.
"target handler" - handler which defined in task target option.

taskHelper: {
  options: {
    handlerByTask: function(options) {
      console.log('[global]handlerByTask'); //task handler
      return true;
    },
     filesArray: [ ]
  },
  js: {
    options: {
      handlerByTask: function(options) {
        console.log('[js]handlerByTask'); //target handler
        return true;
      },
      filesArray: [ ]
    },
    files: [
      { '<%= app.js.src %>/require.js': '<%= bower %>/requirejs/require.js' },
      { expand: true, cwd: '<%= bower %>/bootstrap/js/', src: '**/*.js', dest: '<%= app.js.src %>/bootstrap/' },
      { '<%= app.js.src %>/jquery/jquery.cookie.js': '<%= bower %>/jquery.cookie/jquery.cookie.js' }
    ]
  },
  less: {
    options: {
      filesArray: [ ]
    },
    files: [{ expand: true, cwd: '<%= bower %>/bootstrap/less/', src: '**/*.less', dest: '<%= app.scss.src %>/bootstrap/' }]
  }
},

baka@gentoo ~/test $ grunt taskHelper
Running "taskHelper:js" (taskHelper) task
[js]handlerByTask

Running "taskHelper:less" (taskHelper) task
[global]handlerByTask

Done, without errors.

This is a first type - "target handler" or "task handler".
Call "target handler", if not exist - call "task handler"

I want second type "task handler" and "target handler"
Call "task handler" if exist and that call "target handler" if exist.

Like this

baka@gentoo ~/test $ grunt taskHelper
Running "taskHelper:js" (taskHelper) task
[global]handlerByTask
[js]handlerByTask

Running "taskHelper:less" (taskHelper) task
[global]handlerByTask

Done, without errors.

[anseki]

Ok, I understand it.
But this is mechanism of Grung.
See http://gruntjs.com/configuring-tasks#options

Target-level options will override task-level options.

The plugin get an options that was already overridden by Grunt.
I think, it might be able to access to options that isn't overridden via getting raw configuring Object. but it may break overriding mechanism of Grung. And in standard usage, it is strange processing.

So, you can specify a same handler which always run.

function globalHandler(options) {
  console.log('globalHandler');
  return true;
}

taskHelper: {
  js: {
    options: {
      handlerByTask: [
        globalHandler,
        function(options) {
          console.log('[js]handlerByTask'); //target handler
          return true;
        }
      ]
    }
  },
  less: {
    options: {
      handlerByTask: globalHandler
    }
  }
}

Running "taskHelper:js" (taskHelper) task
globalHandler
[js]handlerByTask

Running "taskHelper:less" (taskHelper) task
globalHandler

Done, without errors.

handlerByFileSrc, handlerByFile and handlerByContent can too.

[6aKa]

I understand, that bad idea. And not in ideology of grunt.