Feature/Added wakeup method to create instances without call explicitly the constructor #26
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.
Creating an instance with
new
keyword will execute the logic inside the__constructor()
but using::wakeup()
will create the instance, and fill the properties without executing the logic in the__constructor()
.So, having and aggregate
Order
that registers the domain eventOrderCreated
in the constructor:we can do:
This makes the usage of
new
more semantic as we are creating a REAL new instance of the Aggregate not just creating an object, we may need to register some domain events on the creation of the Aggregate.