You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When merging multiple config files it would be very useful to be able to replace an earlier definition with a later one - for example, a stable config with a definition for a stable package being overridden in a dev environment by a dev or beta version of the same package. The current merge implementation identifies the duplicates but then relies on Composer's Solver to find a compatible solution. I suggest a flag to change this with a 'replace' behaviour with 'last defined wins'.
The text was updated successfully, but these errors were encountered:
Introduce a new `extra.merge-plugin.replace` configuration directive
that can be used to change the default conflict resolution mechanism.
When enabled, duplicate package declarations in merged files will
overwrite the declarations made in earlier files. Files are loaded in
the order specified in `extra.merge-plugin.include` with globbed files
being loaded in alphabetical order.
This behavior can be used to replace a default stable package with a dev
or beta version of the same package for testing.
Closeswikimedia#45
When merging multiple config files it would be very useful to be able to replace an earlier definition with a later one - for example, a stable config with a definition for a stable package being overridden in a dev environment by a dev or beta version of the same package. The current merge implementation identifies the duplicates but then relies on Composer's Solver to find a compatible solution. I suggest a flag to change this with a 'replace' behaviour with 'last defined wins'.
The text was updated successfully, but these errors were encountered: