Closed sascha-egerer closed 4 years ago
so the process can continue and update at least all other packages
for me the question is, how the composer library installer handles that case.
I tried it and when --no-interaction
is specified, the installation / update is stopped, which, from a package manager perspective, is the safest thing to do.
So if there are setups where this imposes a problem, these setups should be modified.
I think that depends on the option discard-changes
https://getcomposer.org/doc/06-config.md#discard-changes
Is that possible?
Is that possible?
Yes, true. But in any case composer updates the code (changes are discarded or stashed), or it stops execution. The PR here just ignores the changes and leaves the code in undefined state. That might work for edge cases, but may be harmful in other cases.
I'll re-open the pr, but mark it as needs changes.
Anybody wants to pick up this one and work on the open topics?
If not, I tend to close this again.
I'm fine with closing it.
If a TYPO3 extension has modified files while running composer update the process ends hard with an exception and not further changes are made. Exceptions should be cachtched so the process can continue and update at least all other packages