This repository was archived by the owner on Jul 16, 2025. It is now read-only.
feat: allow JsonSerializable objects in contract #377
Merged
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.
As brought up in #371 it could be a possible extension point to the contract to reintroduce the support for
JsonSerializable
objects when there are no normalizers for an object.So it would be a possible alternative for custom
MessageBagInterface
,MessageInterface
,ContentInterface
, etc. by allowing them to implement theJsonSerializable
interface.