You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Extract the use case business logic to its own Application Service class and execute it from the main entry point
* Create the `AggregateRoot` abstract class in order to deal with recorded domain events being able to pull them out afterwards
* Refactor the `EventBus#publish` contract in order to receive a `List` of `DomainEvent`s instead of a single one. I've tried with the varargs approach in order to be able to publish one single event or a list of them, but it wouldn't match the actual contract of the `AggregateRoot#pullDomainEvents(): List<DomainEvent>` return type. So taking into account we would have to convert it to an `Array` (cost O(n)) just because of that, I think it make sense to just use `List` on the `EventBus` side and simplify the signatures at least for now 🤟
0 commit comments