Add void return types to event callback signatures

Add `: void` to 29 event callback method signatures across Table,
Controller, Component, Helper, and Command documentation.

Author: dereuromark

docs/en/console-commands/commands.md

@@ -619,7 +619,7 @@ The `beforeExecute()` and `afterExecute()` hook methods were added.
 
 ### beforeExecute()
 
-`method` Cake\\Console\\Command::**beforeExecute**(EventInterface $event, Arguments $args, ConsoleIo $io)
+`method` Cake\\Console\\Command::**beforeExecute**(EventInterface $event, Arguments $args, ConsoleIo $io): void
 
 Called before the `execute()` method runs. Useful for initialization and
 validation:
@@ -644,7 +644,7 @@ class MyCommand extends Command
 
 ### afterExecute()
 
-`method` Cake\\Console\\Command::**afterExecute**(EventInterface $event, Arguments $args, ConsoleIo $io)
+`method` Cake\\Console\\Command::**afterExecute**(EventInterface $event, Arguments $args, ConsoleIo $io): void
 
 Called after the `execute()` method completes. Useful for cleanup and
 logging:

docs/en/controllers.md

@@ -561,15 +561,15 @@ methods are implemented by your controllers
 
 #### beforeFilter()
 
-`method` Cake\\Controller\\Controller::**beforeFilter**(EventInterface $event)
+`method` Cake\\Controller\\Controller::**beforeFilter**(EventInterface $event): void
 
 #### beforeRender()
 
-`method` Cake\\Controller\\Controller::**beforeRender**(EventInterface $event)
+`method` Cake\\Controller\\Controller::**beforeRender**(EventInterface $event): void
 
 #### afterFilter()
 
-`method` Cake\\Controller\\Controller::**afterFilter**(EventInterface $event)
+`method` Cake\\Controller\\Controller::**afterFilter**(EventInterface $event): void
 
 In addition to controller life-cycle callbacks, [Components](controllers/components)
 also provide a similar set of callbacks.

docs/en/controllers/components.md

@@ -306,15 +306,15 @@ $controller = $this->getController();
 Components also offer a few request life-cycle callbacks that allow them to
 augment the request cycle.
 
-`method` Class::**beforeFilter**(EventInterface $event)
+`method` Class::**beforeFilter**(EventInterface $event): void
 
-`method` Class::**startup**(EventInterface $event)
+`method` Class::**startup**(EventInterface $event): void
 
-`method` Class::**beforeRender**(EventInterface $event)
+`method` Class::**beforeRender**(EventInterface $event): void
 
-`method` Class::**afterFilter**(EventInterface $event)
+`method` Class::**afterFilter**(EventInterface $event): void
 
-`method` Class::**beforeRedirect**(EventInterface $event, $url, Response $response)
+`method` Class::**beforeRedirect**(EventInterface $event, $url, Response $response): void
 
 <a id="redirect-component-events"></a>
 

docs/en/orm/table-objects.md

@@ -174,7 +174,7 @@ public function afterSaveCommit(Event $event, EntityInterface $entity, ArrayObje
 
 ### initialize
 
-`method` Cake\\ORM\\Table::**initialize**(EventInterface $event, ArrayObject $data, ArrayObject $options)
+`method` Cake\\ORM\\Table::**initialize**(EventInterface $event, ArrayObject $data, ArrayObject $options): void
 
 The `Model.initialize` event is fired after the constructor and initialize
 methods are called. The `Table` classes do not listen to this event by
@@ -214,22 +214,22 @@ This will call the `initializeEvent` when any `Table` class is constructed.
 
 ### beforeMarshal
 
-`method` Cake\\ORM\\Table::**beforeMarshal**(EventInterface $event, ArrayObject $data, ArrayObject $options)
+`method` Cake\\ORM\\Table::**beforeMarshal**(EventInterface $event, ArrayObject $data, ArrayObject $options): void
 
 The `Model.beforeMarshal` event is fired before request data is converted
 into entities. See the [Before Marshal](../orm/saving-data#before-marshal) documentation for more information.
 
 ### afterMarshal
 
-`method` Cake\\ORM\\Table::**afterMarshal**(EventInterface $event, EntityInterface $entity, ArrayObject $data, ArrayObject $options)
+`method` Cake\\ORM\\Table::**afterMarshal**(EventInterface $event, EntityInterface $entity, ArrayObject $data, ArrayObject $options): void
 
 The `Model.afterMarshal` event is fired after request data is converted
 into entities. Event handlers will get the converted entities, original request
 data and the options provided to the `patchEntity()` or `newEntity()` call.
 
 ### beforeFind
 
-`method` Cake\\ORM\\Table::**beforeFind**(EventInterface $event, SelectQuery $query, ArrayObject $options, boolean $primary)
+`method` Cake\\ORM\\Table::**beforeFind**(EventInterface $event, SelectQuery $query, ArrayObject $options, boolean $primary): void
 
 The `Model.beforeFind` event is fired before each find operation. By stopping
 the event, and feeding the query with a custom result set, you can bypass the find
@@ -266,7 +266,7 @@ been replaced with the [Map Reduce](../orm/retrieving-data-and-resultsets#map-re
 
 ### buildValidator
 
-`method` Cake\\ORM\\Table::**buildValidator**(EventInterface $event, Validator $validator, $name)
+`method` Cake\\ORM\\Table::**buildValidator**(EventInterface $event, Validator $validator, $name): void
 
 The `Model.buildValidator` event is fired when `$name` validator is created.
 Behaviors, can use this hook to add in validation methods.
@@ -280,37 +280,37 @@ created and after the `Table::buildRules()` method has been called.
 
 ### beforeRules
 
-`method` Cake\\ORM\\Table::**beforeRules**(EventInterface $event, EntityInterface $entity, ArrayObject $options, $operation)
+`method` Cake\\ORM\\Table::**beforeRules**(EventInterface $event, EntityInterface $entity, ArrayObject $options, $operation): void
 
 The `Model.beforeRules` event is fired before an entity has had rules applied. By
 stopping this event, you can halt the rules checking and set the result
 of applying rules.
 
 ### afterRules
 
-`method` Cake\\ORM\\Table::**afterRules**(EventInterface $event, EntityInterface $entity, ArrayObject $options, $result, $operation)
+`method` Cake\\ORM\\Table::**afterRules**(EventInterface $event, EntityInterface $entity, ArrayObject $options, $result, $operation): void
 
 The `Model.afterRules` event is fired after an entity has rules applied. By
 stopping this event, you can return the final value of the rules checking
 operation.
 
 ### beforeSave
 
-`method` Cake\\ORM\\Table::**beforeSave**(EventInterface $event, EntityInterface $entity, ArrayObject $options)
+`method` Cake\\ORM\\Table::**beforeSave**(EventInterface $event, EntityInterface $entity, ArrayObject $options): void
 
 The `Model.beforeSave` event is fired before each entity is saved. Stopping
 this event will abort the save operation. When the event is stopped the result
 of the event will be returned.
 
 ### afterSave
 
-`method` Cake\\ORM\\Table::**afterSave**(EventInterface $event, EntityInterface $entity, ArrayObject $options)
+`method` Cake\\ORM\\Table::**afterSave**(EventInterface $event, EntityInterface $entity, ArrayObject $options): void
 
 The `Model.afterSave` event is fired after an entity is saved.
 
 ### afterSaveCommit
 
-`method` Cake\\ORM\\Table::**afterSaveCommit**(EventInterface $event, EntityInterface $entity, ArrayObject $options)
+`method` Cake\\ORM\\Table::**afterSaveCommit**(EventInterface $event, EntityInterface $entity, ArrayObject $options): void
 
 The `Model.afterSaveCommit` event is fired after the transaction in which the
 save operation is wrapped has been committed. It's also triggered for non atomic
@@ -320,21 +320,21 @@ not triggered if a transaction is started before calling save.
 
 ### beforeDelete
 
-`method` Cake\\ORM\\Table::**beforeDelete**(EventInterface $event, EntityInterface $entity, ArrayObject $options)
+`method` Cake\\ORM\\Table::**beforeDelete**(EventInterface $event, EntityInterface $entity, ArrayObject $options): void
 
 The `Model.beforeDelete` event is fired before an entity is deleted. By
 stopping this event you will abort the delete operation. When the event is stopped the result
 of the event will be returned.
 
 ### afterDelete
 
-`method` Cake\\ORM\\Table::**afterDelete**(EventInterface $event, EntityInterface $entity, ArrayObject $options)
+`method` Cake\\ORM\\Table::**afterDelete**(EventInterface $event, EntityInterface $entity, ArrayObject $options): void
 
 The `Model.afterDelete` event is fired after an entity has been deleted.
 
 ### afterDeleteCommit
 
-`method` Cake\\ORM\\Table::**afterDeleteCommit**(EventInterface $event, EntityInterface $entity, ArrayObject $options)
+`method` Cake\\ORM\\Table::**afterDeleteCommit**(EventInterface $event, EntityInterface $entity, ArrayObject $options): void
 
 The `Model.afterDeleteCommit` event is fired after the transaction in which the
 delete operation is wrapped has been is committed. It's also triggered for non

docs/en/views/helpers.md

@@ -377,24 +377,24 @@ does not implement any of the callback methods.
 
 #### beforeRenderFile()
 
-`method` Helper::**beforeRenderFile**(EventInterface $event, $viewFile)
+`method` Helper::**beforeRenderFile**(EventInterface $event, $viewFile): void
 
 #### afterRenderFile()
 
-`method` Helper::**afterRenderFile**(EventInterface $event, $viewFile, $content)
+`method` Helper::**afterRenderFile**(EventInterface $event, $viewFile, $content): void
 
 #### beforeRender()
 
-`method` Helper::**beforeRender**(EventInterface $event, $viewFile)
+`method` Helper::**beforeRender**(EventInterface $event, $viewFile): void
 
 #### afterRender()
 
-`method` Helper::**afterRender**(EventInterface $event, $viewFile)
+`method` Helper::**afterRender**(EventInterface $event, $viewFile): void
 
 #### beforeLayout()
 
-`method` Helper::**beforeLayout**(EventInterface $event, $layoutFile)
+`method` Helper::**beforeLayout**(EventInterface $event, $layoutFile): void
 
 #### afterLayout()
 
-`method` Helper::**afterLayout**(EventInterface $event, $layoutFile)
+`method` Helper::**afterLayout**(EventInterface $event, $layoutFile): void