To explain, a common layout is to store all your team's custom modules in sites/blah/modules/custom. This is often the only set of modules that a team cares about while developing a site. It would be nice to have a test suite run one command, and know that it always covered the relevant modules (without having to update some secondary list of modules from the drush command, which might get out of sync :)

drush coder --subdir=sites/all/modules/custom,sites/themes/custom

Cheers!

Comments

patcon’s picture

patcon commented
Priority: Normal » Minor

In the meantime, I'm planning to use this to get the module names. Embarrassed to say I hadn't thought of this simple solution before posting!

LIST=$(ls -w1 sites/all/modules/custom/)
drush coder xml $LIST
douggreen’s picture

douggreen commented
Status: Active » Fixed

Should work now, please try the latest dev version.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.

patcon’s picture

patcon commented

Thanks Doug!