Assimilate Event Sourcing functionality into regular aggregates #447
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.
So far, Event Sourced Aggregate was a segarate domain element with its own class and factory. This causes a few issues:
This commit merges the functionality and introduces an option called
is_event_sourced
on BaseAggregate to control event sourcing behavior. The repository will remain as-is for now, because that's where event sourced aggregates primarily differ from regular aggregates. This will need to be revisited if we want to support custom event sourced repositories.