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
"Event dispatch queue" is unnecessarily busy name and can be misleading. "Dispatcher" is more simple and more common in general. When implementing synchronous event dispatching, this name makes more sense.
introduce new handling-related functionality leading to better framework integration: separate interafaces for handler type resolving, handler providing and invoking Middleware context; reworked message handling #18
Maintenance
Refactoring
Better naming
"Event dispatch queue" is unnecessarily busy name and can be misleading. "Dispatcher" is more simple and more common in general. When implementing synchronous event dispatching, this name makes more sense.
Integration test
Release version 0.10
Architecture overhaul
Middleware context:
Handling through middlleware with context:
Other:
SubscriberSpecificDomainEvent
Use new middleware stack #19Release version 0.11
Release version 0.12
Implementation
,EventBus\IEventDispatcher
is weird etc. Namespaces and naming #21Release version 0.13
Release version 1.0
The text was updated successfully, but these errors were encountered: