b8ef7e7332
The semantics of property paths are now:
(1) if a property path is set, it is _always_ respected (relative to the object
of the parent field)
(2) if no property path is set, the object of the parent field is _always_ ignored
Fact (2) allows us to set data into fields that is updated independently of the parent
field (like CSRF tokens, subforms with different objects etc.)
What is missing now is support for subfields that pass the object of the parent field
through to their own subfields. This functionality would be needed for GoogleMapFields,
DateRangeFields etc., which are compositions of individual fields that update the
parent object of the FieldGroup.
There are several alternatives for the latter functionality that should be discussed
in a RFC.
|
||
|---|---|---|
| .. | ||
| BrowserKit | ||
| Console | ||
| CssSelector | ||
| DependencyInjection | ||
| DomCrawler | ||
| EventDispatcher | ||
| Finder | ||
| Form | ||
| HttpFoundation | ||
| HttpKernel | ||
| Routing | ||
| Security | ||
| Templating | ||
| Translation | ||
| Validator | ||
| Yaml | ||