From 6b146f5195dbe0bab7574ea16ea2468f75fceaf9 Mon Sep 17 00:00:00 2001 From: Jordi Boggiano Date: Wed, 21 Jun 2023 13:54:24 +0200 Subject: [PATCH] Update plugins testing info Refs https://github.com/composer/composer/issues/6485#issuecomment-1525807064 --- doc/articles/plugins.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/doc/articles/plugins.md b/doc/articles/plugins.md index 818011887..019ab5d45 100644 --- a/doc/articles/plugins.md +++ b/doc/articles/plugins.md @@ -284,6 +284,10 @@ Now the `custom-plugin-command` is available alongside Composer commands. Plugins for an event can be run manually by the `run-script` command. This works the same way as [running scripts manually](scripts.md#running-scripts-manually). +If it is another type of plugin the best way to test it is probably using a [path repository](../05-repositories.md#path) +to require the plugin in a test project, and then `rm -rf vendor && composer update` +every time you want to install/run it again. + ## Using Plugins Plugin packages are automatically loaded as soon as they are installed and will