Detect appropriate config file to inject config provider into #80
Description
Feature Request
| Q | A |
|---|---|
| New Feature | yes |
| RFC | yes |
| BC Break | no |
Summary
It would be nice if the component installer could work out if a dependency should (probably) be injected into the development or production config file and use this as the default choice presented to the user.
I'm not 100% sure how this could be done. Perhaps check the keywords for the package being installed (see https://getcomposer.org/doc/04-schema.md#keywords)?