Update plugins testing info
Refs https://github.com/composer/composer/issues/6485#issuecomment-1525807064pull/11556/head
parent
bbea3e5284
commit
6b146f5195
|
@ -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
|
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).
|
[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
|
## Using Plugins
|
||||||
|
|
||||||
Plugin packages are automatically loaded as soon as they are installed and will
|
Plugin packages are automatically loaded as soon as they are installed and will
|
||||||
|
|
Loading…
Reference in New Issue