Bug #7049
PropertyMapper tries to change value objects when mapping
| Status: | Resolved | Start date: | 2010-03-29 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assigned To: | Karsten Dambekalns | % Done: | 100% |
|
| Category: | Property | |||
| Target version: | TYPO3 Flow Base Distribution - 1.0 alpha 8 | Estimated time: | 2.00 hours | |
| PHP Version: | Complexity: | |||
| Has patch: | Affected Flow version: |
Description
When the PropertyMapper receives data that ends up in an value object and it detects values to apply after reconstitution it tries to call map(). But value objects are immutable and thus have no setters, this ends up in mapping errors. it should build a new value object instead.
Associated revisions
[+BUGFIX] FLOW3 (Property): Value objects are no longer map()ped built built from scratch in transformToObject(), fixes #7049.
History
#1 Updated by Karsten Dambekalns over 5 years ago
- Status changed from Accepted to Resolved
- % Done changed from 0 to 100
Applied in changeset r4019.