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
This may already be a known issue:
If you create an event class by the same name but in different namespaces and emit them from different aggregates eventflow doesn't exactly know when it rehydrates the event which aggregate the event should reapply to and can pick the wrong one. The easy work around is just to not reuse event names, though something to consider in future releases to maybe see about leveraging the associated aggregate name/type in the metadata.
The text was updated successfully, but these errors were encountered:
This may already be a known issue:
If you create an event class by the same name but in different namespaces and emit them from different aggregates eventflow doesn't exactly know when it rehydrates the event which aggregate the event should reapply to and can pick the wrong one. The easy work around is just to not reuse event names, though something to consider in future releases to maybe see about leveraging the associated aggregate name/type in the metadata.
The text was updated successfully, but these errors were encountered: