Repository navigation
Reduce console output #5
Description
ARRRR! Using this plugin, the Cap'n is a bit too talkative for me - it would be nice to have a way to not hear anything from him (including the CaptainHook Composer Plugin line) or only hear from him when something has actually been done within a call of composer update or install.
It's probably just one of my weird OCD symptoms but I would prefer if there is no output when it just reports that all of the hooks are already installed - it just weirds me out a bit having so much additional output after an ordinary composer update.
Maybe this could be done by setting an option in the extra section of composer.json with a few different values, among them one that will never output anything and one that will only output stuff when there have actually been any changes to the actual hooks.
Activity
sebastianfeldmann commentedon May 1, 2020
Sounds doable, I'll have a look at it
sebastianfeldmann commentedon May 1, 2020
The
captainhook installcommand does currently not abide to thecaptainhook.jsonverbosity setting.Would it be suffice for you if that would be the case so you could configure verbosity there?
This is my composer update output after fixing it locally and setting the Captains verbosity to
quiet?aleksblendwerk commentedon May 1, 2020
If it's up to me I'd rather have no output at all when the plugin calls the install command and no changes are done to the hook files.
If I am getting this right if I set the
verbositysetting in the config toquiet, the actual hook actions don't output anything any more either and just silently fail. That's not what I'd want it to do.Sorry for being such a pain... :)
Maybe the verbosity of the plugin should be configurable in the
extrasection ofcomposer.jsoninstead, same as the already existing plugin options?sebastianfeldmann commentedon May 1, 2020
No pain at all, I totally get it. I will think about it a bit more and see what I can come up with.