Allan Paiste

Hi there! Unfortunately, this is currently not part of the plugin. I've not explored this in-depth, but targeting composer.json will definitely be trickier as it's so central to the whole...

Note taken + many thanks for the fix provided! will be addressing this this weekend!

Most fool-proof solution: Start tracking the - are patches applied or not based on comparing if the file-tree has changes - to see if the actual code has changes or...

The module works off of patching files that Composer packages provide. This means that the patches are basically always applied to the contents of vendor folder. In your case I...

As for the default behaviour of Bundled patch applier: it's using vendor folder as the CWD and resolve targets from the contents of the patch file. In your situation there'll...

Ah yes! it's based on github diff :) This actually gave me an idea :) Would be cool to be able to transform the paths in remote patch of a...

Note taken. I'd take this happens when you initially install the plugin or was it already present? doing this with **--no-plugins** would probably help, but it's still a bug :)

This looks worrisome! So it's the downloader not returning a promise in certain cases :/ Will try to repeat with the same setup and will get back to you with...

Great explanation @angelomaragna! I guess one thing to aid the situation would be to at least give better feedback in form of an error where the plugin would just notify...

I guess we could still have some kind of hint, etc added when encountering this to make it easier to solve :)