codeparty/derby — pull request #438 by cray0000 (2014-06-16 16:40:56+00:00)
Title: [components] Fix setting attributes into scoped model on component init

Related to #418
There are couple of cases when attribute's original path can not be resolved (when attribute is ParentWrapper):
1. When passing the same attribute from one component into another, like described in #418.
2. When having some complicated argument's value, like
```html

```
**currently those kind of attributes end up being ParentWrappers inside component's model**

While there is probably a solution to the 1st case, I don't think there is a simple solution to the 2nd one (it can be implemented in theory though - by automatically creating a reactive functions for this kind of argument values or something like that).
So when ParentWrapper attribute fails to resolve it's original path for creating a ref we should at least init component's model with its renderValue.