Removing projects has no fallbacks

[ao2]

Hi,

when a new patch is detected in the main composer.json, composer-patches removes the target project and reinstall it to apply the patches cleanly, e.g.:

...
Removing package drupal/syntaxhighlighter so that it can be re-installed and re-patched.
...

However it happened to me that the removed project was the one I was working on, and I lost some of the work I did.

Is there a way to prevent that? Maybe composer-patches could make a backup of the project before removing it? Or refuse to remove it if there is a .git directory in it?

Maybe this is more of a generic composer issue?

Thanks,
Antonio

[cweagans]

I'm not opposed to making this configurable in 2.0.0. Added to the roadmap (#93)

[cweagans]

main doesn't do this automatically anymore. It's an explicit action.

I would still recommend not working on things in this way though. composer lets you define things like so:

{
[...]
  "repositories": [
    {
      "type": "path",
      "url": "../../../../"
    }
  ],
  "require": {
    "cweagans/composer-patches": "*@dev",
    "cweagans/composer-patches-testrepo": "~1.0"
  },
[...]
}

(example is taken from the tests on main -- the ../../../../ is the path to where composer-patches exists on disk)

When you do a composer install, it will symlink your local repo into place. That way, if the dep is uninstalled, you don't lose your work. It just deletes the symlink.