yvoyer/domain-event

domain-event's Issues

Provide a default mapping for event in doctrine

Allow to define table definition for user that use DBAL

Add Support for Symfony 5

Error: Class 'Symfony\Component\EventDispatcher\Event' not found

/var/www/project/vendor/star/domain-event/src/Ports/Symfony/EventAdapter.php:17
/var/www/project/vendor/symfony/error-handler/DebugClassLoader.php:337
/var/www/project/vendor/star/domain-event/src/Ports/Symfony/SymfonyPublisher.php:37
/var/www/project/vendor/star/domain-event/src/Ports/Symfony/SymfonyPublisher.php:75
/var/www/project/src/ProductInventory/Infrastructure/EventStore/ProductEventStore.php:40
/var/www/project/src/ProductInventory/Domain/Commands/Product/RegisterProductHandler.php:23
/var/www/project/src/Core/Application/Messaging/ClassMapCommands.php:29
/var/www/project/tests/Functional/Http/Fixtures/ApiFixture.php:38
/var/www/project/tests/Functional/Http/Fixtures/ApiFixture.php:29
/var/www/project/tests/Functional/Http/Controller/ProductShowTest.php:21

use Symfony\Contracts\EventDispatcher\Event;

Add support for ordering on pushed_on column

When rewriting history of events in a store, we might need to push or remove events.
When pushing new events, only fetching by version can cause conflicts with the date.
We should load the event of the aggregate using an order on pushed_on, version ASC to avoid conflict, and more control on the fetch.

Remove dependency to EventDispatcher <=4.4

Following comment we should remove the support for event dispatcher <=4.4 in a future release.

Cannot use the EventPublisher in a symfony application

I get an error must be an instance of MyApp\Event instance of Star\Component\DomainEvent\Symfony\EventAdapter given when using the symfony dispatcher in my app.

// services.yml
services:
    app.event_publisher:
        class: Star\Component\DomainEvent\Symfony\SymfonyPublisher
        arguments:
            - '@event_dispatcher'

    MyApp\MyListener:
        tags:
            - { name: 'kernel.event_subscriber' }

Use microseconds in pushed_on column

doctrine/dbal#2873

In order to add more precision to the added event registration, add microsecond to the pushed_on field.

• Remove version
• Replace ordering of events of an aggregate to used pushed_on alone

Triggering multiple times an event do not propagate it twice

Step to reproduce

1. Call twice the aggregate method which adds a mutation
2. collect events

Expected result
The collected events count should be 2

Actual result
The collected events count is 1

This has the effect of not publishing twice the event when given to the EventPublisher

Switch payload in event to use json instead of serialized array

When using JSON, we can fetch data using JSON in query instead of having to pass throught php to read data.

Mutating to another state inside a mutation do not keep the order of events

Steps to reproduce:

• Creating aggregate: with event AggregateWasCreated
• Call $this->mutate(new OtherEvent())Inside onAggregateWasCreated()

When collecting uncommited events, the order is not reflecting the execution

$aggregate = Aggregate::create();
$events = $aggregate->uncommitedEvents(); 
// $events[0] => OtherEvent
// $events[1] => AggregateWasCreated