DumpListener
in package
implements
EventSubscriberInterface
Configures dump() handler.
Tags
Interfaces, Classes and Traits
- EventSubscriberInterface
- An EventSubscriber knows itself what events it is interested in.
Table of Contents
- $cloner : mixed
- $connection : mixed
- $dumper : mixed
- __construct() : mixed
- configure() : mixed
-
getSubscribedEvents()
: array<string, string|array{0: string, 1: int}|list
- Returns an array of event names this subscriber wants to listen to.
Properties
$cloner
private
mixed
$cloner
$connection
private
mixed
$connection
$dumper
private
mixed
$dumper
Methods
__construct()
public
__construct(ClonerInterface $cloner, DataDumperInterface $dumper[, Connection|null $connection = null ]) : mixed
Parameters
- $cloner : ClonerInterface
- $dumper : DataDumperInterface
- $connection : Connection|null = null
Return values
mixed —configure()
public
configure() : mixed
Return values
mixed —getSubscribedEvents()
Returns an array of event names this subscriber wants to listen to.
public
static getSubscribedEvents() : array<string, string|array{0: string, 1: int}|list>
The array keys are event names and the value can be:
- The method name to call (priority defaults to 0)
- An array composed of the method name to call and the priority
- An array of arrays composed of the method names to call and respective priorities, or 0 if unset
For instance:
- ['eventName' => 'methodName']
- ['eventName' => ['methodName', $priority]]
- ['eventName' => [['methodName1', $priority], ['methodName2']]]
The code must not depend on runtime state as it will only be called at compile time. All logic depending on runtime state must be put into the individual methods handling the events.