PHPackages                             pinoven/event-dispatcher - PHPackages - PHPackages  [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register)

1. [Directory](/)
2. /
3. [Utility & Helpers](/categories/utility)
4. /
5. pinoven/event-dispatcher

ActiveLibrary[Utility & Helpers](/categories/utility)

pinoven/event-dispatcher
========================

A PSR events standard implementation in the oven.

00PHPCI failing

Since Aug 1Pushed 5y ago1 watchersCompare

[ Source](https://github.com/rbergDrox/pinoven-event-dispatcher)[ Packagist](https://packagist.org/packages/pinoven/event-dispatcher)[ RSS](/packages/pinoven-event-dispatcher/feed)WikiDiscussions master Synced yesterday

READMEChangelogDependenciesVersions (1)Used By (0)

Pinoven: Event Dispatcher [![Pinoven](https://camo.githubusercontent.com/6f8151418915d23981722688cf5892e920e1696ace792476504d48116c1ec552/68747470733a2f2f636972636c6563692e636f6d2f67682f726265726744726f782f70696e6f76656e2d6576656e742d646973706174636865722e7376673f7374796c653d737667)](https://circleci.com/gh/rbergDrox/pinoven-event-dispatcher/tree/master)
====================================================================================================================================================================================================================================================================================================================================================================

[](#pinoven-event-dispatcher--)

[PSR-14: Event Dispatcher](https://github.com/php-fig/event-dispatcher) compatible. Implement event dispatcher to dispatch events. It provides a way to register listeners and subscribe/unsubscribe many listeners providers. Dispatcher can retrieve listeners through different providers by using an aggregator.

Features/Usage
==============

[](#featuresusage)

Dispatcher
----------

[](#dispatcher)

```
    use Pinoven\Dispatcher\Dispatch\EventDispatcher;
    use Pinoven\Dispatcher\Provider\AggregatorProvider;
    use Pinoven\Dispatcher\Samples\EventSampleA;

    $aggregator = new AggregatorProvider();
    $eventDispatcher =  new EventDispatcher($aggregator);
    $event = new EventSampleA();
    $eventDispatcher->dispatch($event);
```

Aggregator, Delegate, Mapper Setup
----------------------------------

[](#aggregator-delegate-mapper-setup)

```
    use Fig\EventDispatcher\DelegatingProvider as FigDelegatingProvider;
    use Pinoven\Dispatcher\Listener\ProxyListeners;
    use Pinoven\Dispatcher\Provider\AggregatorProvider;
    use Pinoven\Dispatcher\Provider\DelegatingProvider;
    use Pinoven\Dispatcher\Samples\EventMapperProviderSample;
    use Pinoven\Dispatcher\Samples\EventMapperProviderSampleB;
    use Pinoven\Dispatcher\Samples\EventMapperProviderSampleC;
    use Pinoven\Dispatcher\Samples\EventSampleA;

    $aggregator = new AggregatorProvider();
    $proxy = new ProxyListeners();
    $defaultListenerProvider = new FigDelegatingProvider();
    $eventMapper1 = new  EventMapperProviderSample($proxy);
    $eventMapper2 = new  EventMapperProviderSampleB($proxy);
    $eventMapper3 = new  EventMapperProviderSampleC($proxy);
    $defaultListenerProvider->addProvider($eventMapper3, [EventSampleA::class]);
    $delegateListenerProvider1 = new DelegatingProvider();
    $delegateListenerProvider1->subscribe($eventMapper1);
    $delegateListenerProvider1->subscribe($eventMapper2);
    // \Pinoven\Dispatcher\Provider\DelegatingType() Can take a default listenerProvider.
    $delegateListenerProvider2 = new DelegatingProvider($defaultListenerProvider);
    $aggregator->addProvider($delegateListenerProvider1);
    $aggregator->addProvider($delegateListenerProvider2);
```

Mapper for Event/Listeners
--------------------------

[](#mapper-for-eventlisteners)

```
use Pinoven\Dispatcher\Event\EventListenersMapper;
EventListenersMapper::class;
```

It helps to declare the event type and related listeners.

```
use Pinoven\Dispatcher\Event\EventListenersMapper;
EventListenersMapper::class;
```

Emit Event
----------

[](#emit-event)

```
use Pinoven\Dispatcher\Event\EventEmitter;
EventEmitter::class;
```

Emitter event permit to use the dispatcher and send a custom event too by using string and payload.

Order/Prioritize
----------------

[](#orderprioritize)

### Order items

[](#order-items)

To manage sorting on providers, listeners you have to implement:

```
use Pinoven\Dispatcher\Priority\PrioritizeInterface;
class Prioritize implements PrioritizeInterface
{
    public function sortItems(iterable $items) : iterable
    {
        // Code ...
         return  $items;
    }
}
```

See the implementation

```
use Pinoven\Dispatcher\Priority\Prioritize;
$prioritize = new Prioritize();
```

### Handle Priority

[](#handle-priority)

If the listener is a class then it should implement:

```
use Pinoven\Dispatcher\Priority\ItemPriorityInterface;
ItemPriorityInterface::class;
```

If your listener/callable cannot directly implement this interface you can wrap by using:

```
use Pinoven\Dispatcher\Priority\CallableInterface;
CallableInterface::class;
```

You may need to do some stuff on the wrapper, so you can use the factory to transformer your listener/callable to wrapper item.

```
use Pinoven\Dispatcher\Priority\CallableItemPriorityInterface;
CallableItemPriorityInterface::class;
```

Todo
====

[](#todo)

- merge payload if `public $payload` or add data to existing payload
- Automatic event hierarchy. It means by dealing with BeforeEvent, AfterEvent. Perhaps BetweenEvent.??
- Implement Logger
- Implement Container
- Implement CacheInterface
- Attach/detach Listener ?
- Implement own Collection/Generator
- Clean Sample

Contribution
============

[](#contribution)

- Create issue: improvement + the reason why it should be implemented or issue + how to reproduce.
- Create pull request and explain the issue.

More information will come about how to contribute on all pinoven package.

###  Health Score

16

—

LowBetter than 5% of packages

Maintenance20

Infrequent updates — may be unmaintained

Popularity0

Limited adoption so far

Community7

Small or concentrated contributor base

Maturity32

Early-stage or recently created project

 Bus Factor1

Top contributor holds 100% of commits — single point of failure

How is this calculated?**Maintenance (25%)** — Last commit recency, latest release date, and issue-to-star ratio. Uses a 2-year decay window.

**Popularity (30%)** — Total and monthly downloads, GitHub stars, and forks. Logarithmic scaling prevents top-heavy scores.

**Community (15%)** — Contributors, dependents, forks, watchers, and maintainers. Measures real ecosystem engagement.

**Maturity (30%)** — Project age, version count, PHP version support, and release stability.

### Community

Maintainers

![](https://avatars.githubusercontent.com/u/11984931?v=4)[Raphaël BERGINA](/maintainers/rbergDrox)[@rbergDrox](https://github.com/rbergDrox)

---

Top Contributors

[![rbergDrox](https://avatars.githubusercontent.com/u/11984931?v=4)](https://github.com/rbergDrox "rbergDrox (46 commits)")

---

Tags

event-dispatcherphppinovenpsr-14

### Embed Badge

![Health badge](/badges/pinoven-event-dispatcher/health.svg)

```
[![Health](https://phpackages.com/badges/pinoven-event-dispatcher/health.svg)](https://phpackages.com/packages/pinoven-event-dispatcher)
```

###  Alternatives

[jkuchar/multiplefileupload

Multiple upload form control for Nette framework.

104.4k1](/packages/jkuchar-multiplefileupload)[murilo-perosa/domain-tools

Handle domains and DNS tools.

122.7k](/packages/murilo-perosa-domain-tools)[typisttech/wp-admin-notices

A simplified OOP implementation of the WordPress admin notices

141.2k](/packages/typisttech-wp-admin-notices)

PHPackages © 2026

[Directory](/)[Categories](/categories)[Trending](/trending)[Changelog](/changelog)[Analyze](/analyze)