You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ideally phake would use the following order of precedence to determine which task to run:
A task with the exact name within the current or named group
The default task in the current group
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:
Running phake run would execute run
Running phake default would execute default
Running phake would execute default
Running phake db:init would execute db:init
Running phake db:default would execute db:default
Running phake db would execute db:default
Running phake test:init would execute test:init
Running phake test:default would execute test:default
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.
The text was updated successfully, but these errors were encountered:
Ideally phake would use the following order of precedence to determine which task to run:
That means if I have tasks for
default
,build
,run
,test
,deploy
,db:init
,db:update
,db:delete
anddb:default
,test:init
,test:run
, andtest:default
, the following behaviour is expected:phake run
would executerun
phake default
would executedefault
phake
would executedefault
phake db:init
would executedb:init
phake db:default
would executedb:default
phake db
would executedb:default
phake test:init
would executetest:init
phake test:default
would executetest:default
phake test
would executetest
(there's a named task calledtest
which has higher precedence thantest:default
)As far as I can tell, that mimics the behaviour of the root
:default
task fairly closely without breaking compatibility with existing Phakefiles.The text was updated successfully, but these errors were encountered: