Cameron Eagans

``` "the/project": [ { "description": "This is the description of the patch", "url": "https://www.example.com/path/to/file.patch", "depth": 2 } ] ``` would let you set it for that specific patch. However, patch...

Opened https://github.com/cweagans/composer-patches/issues/582 to capture the annoying compact -> expanded format conversion.

No, 2.x works completely differently. Give it a go. Depth of 1 is the base default in 2.x as well (since that's the default for git apply).

I'm on board. Maybe we can add another config value 'allow-dependency-patches' and have that act as an allow list if set. I don't want to have to set both. Having...

You can just disable the resolver - no need to try to make an allow list work for that :)

No worries. Same thing here - I'll update here if I beat you to it!

Correct. If the option is NOT defined, all dependencies will be scanned for patches. If it IS defined, only the listed packages will be scanned.

@Natshah All composer patches config is nested inside of a `extra.composer-patches` to avoid naming conflicts like that. As an aside, you might be interested in https://github.com/cweagans/composer-configurable-plugin/ as a replacement for...

> I then introduce a new patch on my local. How are you doing this? Just adding it manually to composer.json and then ___ ? You should not have to...

Need some time to grok it all. I think you might be doing something wrong but I want to understand more fully before I make that assertion :)