Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Observation: Events by the same name in different namespaces targeting different aggregates won't work #903

Closed
fratting opened this issue Sep 14, 2021 · 2 comments
Labels

Comments

@fratting
Copy link

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.

@rasmus
Copy link
Member

rasmus commented Oct 20, 2021

Its a known issue, to give your events custom names with e.g. a domain prefix, use the [EventVersion] attribute as documented here https://docs.geteventflow.net/GettingStarted.html#event

@rasmus
Copy link
Member

rasmus commented Mar 4, 2022

Closing this as there's a work-round and an issue on improving it #907

@rasmus rasmus closed this as completed Mar 4, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants