Use custom serializer while persisting events #464
Merged
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
freekmurze
requested changes
May 27, 2024
src/StoredEvents/Repositories/EloquentStoredEventRepository.php
Outdated
Show resolved
Hide resolved
|
@freekmurze I added a test, let me know if this works for you 😄 |
|
Thanks! |
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.
I stumbled upon issue #414 while setting up custom event serializers.
This PR fixes this issue by also using the custom event serializer while persisting events.
If you have any questions, please reach out to me!
Note About Versioning
I don't know if the previous behavior was a bug or intentional, but "fixing" it changes how events are serialized into the database. Therefore, it probably makes sense to release this in a major version update.