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
Same as for the callSubsequentAggregateFunction context provider should receive the $aggregateState when $this->createAggregate is false.
It's also not clear from the documentation, neither from the code what are the possible arguments for context providers, and aggregate handlers: this should be better communicated.
The text was updated successfully, but these errors were encountered:
Event engine only passes the current command to a context provider. I get your idea and agree that it could be useful, but changing the behavior would require a change in the Flavour interface and that's something I'd like to avoid at the moment.
As an alternative you can inject the Event Engine into your context provider and get the aggregate state from it. Aggregate state is cached in memory until next save happens, so Event Engine won't load the state twice.
Same as for the
callSubsequentAggregateFunction
context provider should receive the$aggregateState
when$this->createAggregate
is false.It's also not clear from the documentation, neither from the code what are the possible arguments for context providers, and aggregate handlers: this should be better communicated.
The text was updated successfully, but these errors were encountered: