You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@deviantintegral: regarding https://architecture.lullabot.com/adr/20220429-composer-patches-inline/ ... and considering we have a tool like Drainpipe, why not allow the user to use a different patch file and join the composer file with the patches file at the moment of validation? composer.json already has enough information, and if we can have a separation for patches and have a full validation of the composer contents, that would be the best scenario for developers.
While we probably shouldn't enforce these ADRs, we could certainly log a warning if any of these configurations are not as expected.
I think we could do this in a composer install hook?
https://architecture.lullabot.com/adr/20220429-composer-patchlevel/
https://architecture.lullabot.com/adr/20220429-composer-patches-inline/
https://architecture.lullabot.com/adr/20220429-composer-patch-files/
https://architecture.lullabot.com/adr/20220429-composer-exit-failure/
The text was updated successfully, but these errors were encountered: