Make it possible to set preserve-paths in dependency extras. #22
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue:
I use a CMS which uses composer for extension management. In this implementation sometimes only the package name is known. Therefore the installed package is always wrapped in a new root package which has the package to install as dependency. Unfortunately this root package has none of the
extra
my package has and I can not change it. Therefore I can not use this plugin at the moment.Solution:
Make it possible to get the preserve paths from the dependencies. To ensure that this causes no new issues, I added two new options. A package has to declare that his preserve paths should be read if it is used as dependency (
preserve-paths-as-dependency
). Additionally anyone who uses your plugin can override this behavior in your root package by settingpreserve-paths-ignore-dependencies
to true. In this case no information will be read for any of the dependencies.I would be glad if you could include this, but it would also be ok for me if you decide that this is too specific and you do not want to have this change.