public-mirrors
/
composer
mirror of https://github.com/composer/composer
1
0
Fork 0
Code

Update plugin documentation (#11813)

pull/11895/head
PrinsFrank 2024-02-06 12:57:34 +01:00 committed by GitHub
parent d3aeb1357f
commit 8a69c0555b
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
doc/articles/plugins.md
View File

@ -271,6 +271,8 @@ class Command extends BaseCommand
protected function execute(InputInterface $input, OutputInterface $output): int protected function execute(InputInterface $input, OutputInterface $output): int
{ {
$output->writeln('Executing'); $output->writeln('Executing');
return 0;
} }
} }
``` ```
@ -285,7 +287,7 @@ Plugins for an event can be run manually by the `run-script` command. This works
[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) 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` to require the plugin in a test project. If you are developing locally and want to test frequently, you can make sure the path repository uses symlinks, as changes are updated immediately. Otherwise, you'll have to run `rm -rf vendor && composer update`
every time you want to install/run it again. every time you want to install/run it again.
## Using Plugins ## Using Plugins