Andrianarivony Leon

@rob, this feature is very important in real world application. Let me give some valid argument that we do a million times every days since that we work with aurelia...

@jdanyow, thank you for your support. There is a chance that by naming convention, an array or map can be initialized. ...Items or ...Collection, ...KeyValues This feature is very usefull...

Bases with our expériences, having the option off/on is not really helpful for the développer because it requîtes so much dependencies between plugins on your on apps. This is really...

@jdanyow: I like the idea, for a big app, it will be hard to governe rules for this. By keeping your idea, rather having auto:factory, it will be good to...

For our case, it's always on form control for editing (editor views). A display view doesn't this kind of stuff.... So, make it off and binding behavior proposal with auto:factory...

@EisenbergEffect, If you remove the auto-creates instances by default, it will make many of us really sad. I believe that to disable by default is a better approach. For a...

@Rob, thanks for your clarification, it's what I expected before to ask if it's a bug or not ? So, with the following code: ``` ``` In my child, I...

@Rob, This behavior is very useful but we just need to be careful when we provide guidelines and conventions in our development process. Guess that you have "this.model" naming convention...

@EisenbergEffect To keep compatibility, having a global setting ``` compose-context-behavior = 'Cascading | Block' ``` The default is cascading to make sure that we keep the compatibility. So, for any...