Timeline for How does the `ref` attribute work in Sitecore configuration files?
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 24, 2016 at 13:33 | comment | added | Dmytro Shevchenko | Yes, thank you! I was first confused by what you meant by "property". For some reason, I was thinking about node attributes the whole time! With your expanded explanation, it is now much more clear you meant object properties. | |
| Oct 24, 2016 at 13:31 | comment | added | Matt | I've added some clarification on how child nodes in the XML map to properties on the created objects, and included a simple example. While the answer isn't quite so straight-forward, I believe that it holds for the majority of cases people will encounter. Does that clear things up a bit? | |
| Oct 24, 2016 at 13:29 | vote | accept | Dmytro Shevchenko | ||
| Oct 24, 2016 at 13:26 | history | edited | Matt | CC BY-SA 3.0 |
Clarification over how child nodes in the XML configuration map to properties on the object.
|
| Oct 24, 2016 at 7:32 | comment | added | Matt | Yep, as I say in my answer, it will set the properties first from the "referred" XML and after that it will set the properties contained in the "original" (referring) XML | |
| Oct 23, 2016 at 19:53 | comment | added | Dmytro Shevchenko | Thanks a lot! This was very interesting and useful. How about the children of the referred node? Will the factory use them when creating the object? | |
| Oct 23, 2016 at 19:17 | review | First posts | |||
| Oct 23, 2016 at 20:00 | |||||
| Oct 23, 2016 at 19:17 | history | answered | Matt | CC BY-SA 3.0 |