Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running group should run group:default if it exists and no group task exists #60

Open
kitgrose opened this issue Jun 22, 2016 · 0 comments

Comments

@kitgrose
Copy link

Ideally phake would use the following order of precedence to determine which task to run:

  1. A task with the exact name within the current or named group
  2. The default task in the current group
  3. Error

That means if I have tasks for default, build, run, test, deploy, db:init, db:update, db:delete and db:default, test:init, test:run, and test:default, the following behaviour is expected:

  1. Running phake run would execute run
  2. Running phake default would execute default
  3. Running phake would execute default
  4. Running phake db:init would execute db:init
  5. Running phake db:default would execute db:default
  6. Running phake db would execute db:default
  7. Running phake test:init would execute test:init
  8. Running phake test:default would execute test:default
  9. Running phake test would execute test (there's a named task called test which has higher precedence than test:default)

As far as I can tell, that mimics the behaviour of the root :default task fairly closely without breaking compatibility with existing Phakefiles.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant