dark: fix clone serialization issue in php8.2 #12
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.
Notes
For some reason serializing a cloned object in PHP 8.2 breaks the serialization recursion, resulting in the creation of two different serializables (different references). The serializer only keeps track of the deepest serializable in the chain, meaning that handled serializable properties can only be accessed by doing the following:
Reproduction steps
For reference, here are the serialized values from the
Cloner
test class introduced in this PR without the__clone()
fix: