3 All commandfiles may implement methods that are called by Drush at various times in the request cycle. To implement one, add a `@hook validate` (for example) to the top of your method.
5 - [Documentation about available hooks](https://github.com/consolidation/annotated-command#hooks).
6 - To see how core commands implement a hook, you can [search the Drush source code](https://github.com/drush-ops/drush/search?q=%40hook+validate&type=Code&utf8=%E2%9C%93). This link uses validate hook as an example.
11 Drush commands can define custom events that other command files can hook. You can find examples in [CacheCommands](https://github.com/drush-ops/drush/blob/master/src/Commands/core/CacheCommands.php) and [SanitizeCommands](https://github.com/drush-ops/drush/blob/master/src/Drupal/Commands/sql/SanitizeCommands.php)
13 First, the command must implement CustomEventAwareInterface and use CustomEventAwareTrait, as described in the [dependency injection](dependency-injection.md) documentation.
15 Then, the command may ask the provided hook manager to return a list of handlers with a certain annotation. In the example below, the `my-event` label is used:
18 * This command uses a custom event 'my-event' to collect data. Note that
19 * the event handlers will not be found unless the hook manager is
20 * injected into this command handler object via `setHookManager()`
21 * (defined in CustomEventAwareTrait).
23 * @command example:command
25 public function exampleCommand()
27 $myEventHandlers = $this->getCustomEventHandlers('my-event');
29 foreach ($myEventHandlers as $handler) {
30 $result[] = $handler();
33 return implode(',', $result);
37 Other command handlers may provide implementations by implementing `@hook on-event my-event`.
41 * @hook on-event my-event
43 public function hookOne()