neos / neos/flow-development-collection
Serialization changes the original object
Open
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 143
- Forks
- 191
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 9
Description
Description
If you serialize an object containing related entities in a multivalued property (array or similar), bringing this object to serialization it will remove those entities from the object during serialization, which then will stop you from using the properties value after the serialization.
Steps to Reproduce
See testcase in #2012
Affected Versions
Flow: 4.3 - 6.2
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the test case referenced in issue #2012, then trace the serialization path for objects containing related entities in a multivalued property. Done means serialization no longer removes those entities, so the original object's property remains usable afterward.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100