Nested Collections of Collections / List Tasks by Collection

[thinkwelltwd]

First of all, thanks for the elegant invoke library!

I'm building a cli-based application and am wondering if there's any way to list and run tasks by collection. For example, as the docs have it, tasks in 2 collections are listed like so:

[root@system RedHat]# invoke --list
Available tasks:

  docs.build
  docs.clean
  ship.increment
  ship.release

What I'd prefer is only list the top-level Collections - docs & ship - something like so:

[root@system RedHat]# invoke --list
Available Collections:

  docs
  ship

Then the user could find the available commands by passing in the Collection name and the --list param:

[root@system RedHat]# invoke ship --list
Available tasks:

  increment
  release

And finally, run the desired task as:

[root@system RedHat]# invoke ship release

IMO, that would scale to larger groups of commands much better than a long list that must be piped to grep to view only by collection.

I like the idea of having all Collections available regardless of directory as it enhances discoverability. But then it also increases clutter when there are numerous collections containing numerous tasks. But perhaps I missed something; is such a thing possible already?

[bitprophet]

Yup, I've been having this need myself lately as well so I am highly likely to tackle it as a personal itch-scratch :) It falls under #33 so let's close this in favor of that. I'll bang out some more personal thoughts (and try to remember to take your suggestion under account - it's definitely an angle I have been thinking of myself, "crap which tasks are in the foo sub-namespace again?") in there when I get to it. Thanks!

[thinkwelltwd]

Ok thanks for the response. Will be eager to try out the fix for #33!