Feature request from adragus-inviqa, posted on GitHub Jul 17, 2016
php bin/magento
Magento CLI version 2.1.0
On previous versions, we've been told to use setup:di:compile-multi-tenant
instead of setup:di:compile
. K. Now we're told to get back to using setup:di:compile
. Ugh, fine.
But whilst you were fixing (?) setup:di:compile
, we've gotten accustomed to setup:di:compile-multi-tenant
's various and useful CLI options, which - yep - setup:di:compile
does not have. And now that setup:di:compile-multi-tenant
is gone, we're left with no.. option:
php bin/magento help setup:di:compile
Usage:
setup:di:compile
Options:
--help (-h) Display this help message
--quiet (-q) Do not output any message
--verbose (-v|vv|vvv) Increase the verbosity of messages: 1 for normal output, 2 for more verbose output and 3 for debug
--version (-V) Display this application version
--ansi Force ANSI output
--no-ansi Disable ANSI output
--no-interaction (-n) Do not ask any interactive question
One of the more useful options which is now kaput was --exclude-pattern
. That allowed us to omit certain files which we didn't want compiled, ofc. But now we're stuck with whatever you thought it was good for your scenarios.
Can we get setup:di:compile
to be as flexible as multi-tenant
was? If not the same, at least allow us to inject our own exclude patterns.
PS: I hope I won't be asked "Can you give me an example of a scenario in which you need to exclude something?". Just trust me on this one, mkay?