Fix preserving event order when dispatched from aggregate root via event handler #405
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
added 2 commits
March 31, 2023 14:19
|
@rubenvanassche I think this is fine. Could you double check that this won't result in issues for our client projects? |
|
@sebastiandedeyne, doesn't look like a problem to me, even a solution to some problems, what do you think? |
sebastiandedeyne
approved these changes
Apr 18, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When firing event from reactor, dispatched event should go after event that triggered the reactor. Example:
MoneyAdded -> DoubleBalanceReactor -> MoneyMultipliedcurrently dispatches events to the bus
MoneyMultipliedfirst. This PR fixes that behaviour.