Closed schmunk42 closed 6 years ago
See the section Dreprecated options in the release page.
config.fxp-asset
section will override the options still defined in the extra
sectionAll the options in the config.fxp-asset section will override the options still defined in the extra section
What if I have defined "old" options in extra, like vcs-driver-options
and "new" ones in config
like git-skip-update
, will they get merged?
Only the first key, like the behavior of the array_merge
function, and not like the array_merge_recursive
function, so no.
But if you interested to add this behavior, It's in the method Fxp\Composer\AssetPlugin\Config\ConfigBuilder::injectDeprecatedConfig()
that it happens.
It's related to https://github.com/fxpio/composer-asset-plugin/issues/292 - I refactored some composer.json
files and noticed, that the asset-plugin started to do API requests again, although I've disabled them in the (extra
) config.
Maybe it would be an option to enforce configuration either via extra
(with a warning) or via config
- but if both are specified the plugin would exit with an error. WDYT?
I think it would be better to merge the sub-options between extra
and config
.
Does this mean I should switch ASAP, but it's still recognized - or doesn't it have any affect all now?