PropertyMappingConfiguration::mapUnknownProperties is not passed down to Subconfiguration
|Priority:||Should have||Due date:|
|Assignee:||Sebastian Kurfuerst||% Done:||
|Has patch:||Yes||FLOW3 version affected:||Git 1.1|
if i set allowAllProperties on my PropertyMappingConfiguration it still can fail because the setting doesn't get passed down in line 152 from getConfigurationFor.
I've attached a patch to pass down this setting.
Updated by Marc Neuhaus 12 months ago
- File PropertyMappingConfiguration.diff added
forgot to add the Patch :)
Updated by Bastian Waidelich 12 months ago
- Category set to Property
- Assignee set to Sebastian Kurfuerst
- Target version set to 1.1 beta 2
Sebastian, I assign this to you as you are more into that topic ;)
I had similar issues: especially when working with the Form framework it's really tedious to get the PropertyMappingConfiguration right.. There should be some easy way to disable the pessimistic checks (as the form is secured by HMAC anyways) and/or to allow creation/modification & property changes for nested elements