[5.x] Ability to override how objects are serialized #1562
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.
This pull request introduces a
formatForTelescope
method, allowing developers to override how Telescope formats/serializes their objects.By default, Telescope uses
json_decode(json_encode($object), true)
to format/serialize objects, which takes the object's properties and attempts to JSON serialize them.However, in our case, where
->jsonSerialize()
may return objects which reference the current object, that isn't ideal as it causes an infinite loop.Instead, we'd like to take control of the serialization logic and return an array without any of the "circular relationships".
Related: statamic/cms#10782