1
0
Fork 0
mirror of https://github.com/composer/composer synced 2025-05-10 09:02:59 +00:00

Add detailed notes about events in upgrade guide, add COMPOSER_DEBUG_EVENTS env var for debugging events

This commit is contained in:
Jordi Boggiano 2020-10-13 12:05:24 +02:00
parent cb1c35ab52
commit 3c25d180e6
No known key found for this signature in database
GPG key ID: 7BBD42C429EC80BC
4 changed files with 44 additions and 3 deletions

View file

@ -94,6 +94,10 @@ and have it return an array. The array key must be the
[event name](https://getcomposer.org/doc/articles/scripts.md#event-names)
and the value is the name of the method in this class to be called.
> **Note:** If you don't know which event to listen to, you can run a Composer
> command with the COMPOSER_DEBUG_EVENTS=1 environment variable set, which might
> help you identify what event you are looking for.
```php
public static function getSubscribedEvents()
{
@ -263,7 +267,7 @@ Now the `custom-plugin-command` is available alongside Composer commands.
## Running plugins manually
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).
## Using Plugins