Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for merge-replace option #221

Closed
LukeTowers opened this issue Sep 3, 2021 · 1 comment · Fixed by #233
Closed

Add support for merge-replace option #221

LukeTowers opened this issue Sep 3, 2021 · 1 comment · Fixed by #233

Comments

@LukeTowers
Copy link

LukeTowers commented Sep 3, 2021

It would be great if we could disable the merging of the replace property as it causes issues when the composer.json file being merged from is included by a package that is itself loaded via the main composer.json file. See wintercms/wn-user-plugin#12. Merging these properties were added in #60 but there was no way to disable that functionality.

Failing that it would be good if there was some way to indicate not to merge the configs of any packages that are already included by the main composer.json file since their configs will already be evaluated by Composer when they're required in the main composer.json file.

@eileenmcnaughton
Copy link

This is what I'm looking for too - not sure if using self:version makes a difference - I'm trying it but it's giving me other issues

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants