Sending arguments to hubbed "basic" tasks

[davidgovea]

In a child project, I have a "Basic task" that accepts an argument. From within the child project, I can run:

grunt task:argument

From the "parent" project, I would like to issue a command like:

grunt hub:child:task:argument

but this ends up running the [task, argument] tasks on the child project -> "Task 'argument' not found"

I have found a workaround:

grunt hub:child:'task\:argument'

which ends up running task:argument on the child, but this feels kinda hacky.

Since the 'child' gruntfile is never loaded by grunt-hub, it does not seem feasible to check whether the task exists beforehand - so what is the best option here? A character other than ":"? Perhaps even just documenting this workaround?

Thanks!

[shama]

The solution you found grunt hub:child:'task\:argument' is your best bet. I don't really want to implement a cli convention outside of default grunt at this time.

+1 to documenting this.

[davidgovea]

Great - I thought as much. Who knows what will happen on windows, though...
I can do a PR on the readme for this

Thanks for the quick response

[mrfelton]

+1 for this. the workaround mentioned above works if you are running commands directly from the command line, but not if you are including tasks within registerTask() within Gruntfile.js. ie, you can't do this:

  grunt.registerTask('test_e2e', 'Run e2e tests against all applications.', [
    'hub:client_app:test:e2e',
    'hub:client_docs:test:e2e'
  ]);

or this:

  grunt.registerTask('test_e2e', 'Run e2e tests against all applications.', [
    "hub:client_app:'test\:e2e'",
    "hub:client_docs:'test\:e2e'"
  ]);

or any similar variant that I have tried.