Download the PHP package jmikola/wildcard-event-dispatcher-bundle without Composer
On this page you can find all versions of the php package jmikola/wildcard-event-dispatcher-bundle. It is possible to download/install these versions without Composer. Possible dependencies are resolved automatically.
Download jmikola/wildcard-event-dispatcher-bundle
More information about jmikola/wildcard-event-dispatcher-bundle
Files in jmikola/wildcard-event-dispatcher-bundle
Package wildcard-event-dispatcher-bundle
Short Description Enhances the Symfony2 event dispatcher with support for wildcard patterns inspired by AMQP topic exchanges.
License MIT
Homepage https://github.com/jmikola/JmikolaWildcardEventDispatcherBundle
Informations about the package wildcard-event-dispatcher-bundle
JmikolaWildcardEventDispatcherBundle
This bundle integrates the WildcardEventDispatcher library with Symfony and allows event listeners to be assigned using a wildcard pattern inspired by AMQP topic exchanges.
Symfony's event dispatcher component and the framework's existing convention for event names (dot-separated words) is already quite similar to AMQP message routing keys. This bundle is intended to be used sparingly, where wildcards may replace verbose configuration for central listeners, such as an activity logging service.
Some background info for this bundle may be found on the symfony-devs mailing list.
Compatibility
This bundle requires Symfony 2.3 or above.
Configuration
There are no configuration options. Symfony will load the bundle's dependency injection extension automatically.
The extension will create a service that composes the existing
event_dispatcher
service and assumes its service ID. Depending on whether
debug mode is enabled, this bundle may wrap an instance of FrameworkBundle's
ContainerAwareEventDispatcher
or TraceableEventDispatcher
class.
Listening on Wildcard Event Patterns
This bundle enables you to use the single-word *
and multi-word #
wildcards
when assigning event listeners. The wildcard operators are described in greater
detail in the documentation for WildcardEventDispatcher.
Single-word Wildcard
Consider the scenario where the acme.listener
service is currently listening
on multiple core
events:
You could refactor the above configuration to use the single-word *
wildcard:
This listener will now observe all events starting with core.
and followed by
another word. An event named core
would also be matched by this pattern.
Multi-word Wildcard
Suppose there was an event in your application named core.foo.bar
. The
aforementioned core.*
pattern would not match this event. You could use:
This syntax would match core.foo
and core.foo.bar
, but core
would no
longer be matched (assuming there was such an event); however, the multi-word
#
wildcard would allow all of these event names to be matched:
The #
wildcard could also be used to listen to all events in the
application:
All versions of wildcard-event-dispatcher-bundle with dependencies
jmikola/wildcard-event-dispatcher Version ^1.1.0
symfony/config Version ^2.3 || ^3.0
symfony/dependency-injection Version ^2.3 || ^3.0
symfony/event-dispatcher Version ^2.3 || ^3.0
symfony/http-kernel Version ^2.3 || ^3.0