Fix events stored with no stream_type #32
Closed
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.
This is a bug-fix for #31
The root problem was the fact that when loading events from the DB and creating a new instance of an Entity with stream injected, the
stream_type
property was ignored. In consequence, a new instance was created with emptystream_type
and all of the subsequent events were stored without it.I run the tests before and after the change and it proves the issue is gone now.
Before
After