FR: add white-list options ('white-list:vendor/package1', 'white-list:vendor/package2') about production-dependencies-guard

[kalessil]

Answering myself: whitelisting will do the trick =) I'll implement the feature.

[kalessil]

Implemented!

[kalessil]

While the idea is exactly this, the plugin should rather target customer projects and products.
In the case of an extension or CaptainHook itself, IMO it'll be no value in using the plugin.

[shochdoerfer]

It depends, some checks like check-license or check-abandoned might be even good for library projects. And making sure that dev dependencies do not pollute the require section of the composer.json file could also be interesting for libraries.

[kalessil]

Sounds reasonable.

What about the following scenario: the captain hook plugin brings the guard into a Magento project and it breaks composer update/install (not so well maintained project)?