The commands for this Drush extension involve either cd-ing to the module's directory or supplying it on the command line. Drush has a Drupal Directory command (dd) that can be used to retrieve this. My suggestion is to use it to allow the user to supply the module name and allow drush to get the module directory.
It is possible to do this on the command line now with something like this:
drush bandaid-patch https://www.drupal.org/node/123456 $(drush dd module_name)
What I would like to be able to run is:
drush bandaid-patch https://www.drupal.org/node/123456 module_name
I think that Drupal and drush will supply the correct module location in case of module overrides. Maybe something to check for or possibly run a drush cc drush before searching for the module's directory.
Maybe a fallback is needed. In other words if a path is given then it is used otherwise it checks to see if a module name was given then finds its path.
Thanks for considering this and God Bless!
Frederick
Hi!
The commands for this Drush extension involve either cd-ing to the module's directory or supplying it on the command line. Drush has a Drupal Directory command (dd) that can be used to retrieve this. My suggestion is to use it to allow the user to supply the module name and allow drush to get the module directory.
It is possible to do this on the command line now with something like this:
drush bandaid-patch https://www.drupal.org/node/123456 $(drush dd module_name)What I would like to be able to run is:drush bandaid-patch https://www.drupal.org/node/123456 module_nameI think that Drupal and drush will supply the correct module location in case of module overrides. Maybe something to check for or possibly run a
drush cc drushbefore searching for the module's directory.Maybe a fallback is needed. In other words if a path is given then it is used otherwise it checks to see if a module name was given then finds its path.
Thanks for considering this and God Bless! Frederick