It would be a nice feature, if default values for command options were configurable in a project and being used by zend-expressive-tooling if no explicit argument was provided.
In the following I will describe the case using the modules-path option for the module:create command. Other command options might benefit from the same implementation.
Let's say, we have a project, where the modules-path is not located in the default src but in custom-directory. Then modules-path could be configured as follows (just as an example - not sure, if that is a good option):
It would be a nice feature, if default values for command options were configurable in a project and being used by
zend-expressive-tooling
if no explicit argument was provided.In the following I will describe the case using the
modules-path
option for themodule:create
command. Other command options might benefit from the same implementation.Let's say, we have a project, where the
modules-path
is not located in the defaultsrc
but incustom-directory
. Thenmodules-path
could be configured as follows (just as an example - not sure, if that is a good option):Then one could execute
./vendor/bin/expressive module:create MyModule
instead of needing to provide the modules-path each time
./vendor/bin/expressive module:create MyModule --modules-path custom-directory
.It should still be possible, to provide an option value overwriting the configured default:
./vendor/bin/expressive module:create MyModule --modules-path another-custom-directory
.