Makes attribute arguments passed to a component two way binding

[justinbmeyer]

If you have a "master" component with a scope value like:

scope: {
  visible: true
}

Pass that property to a low-level compute like:

<low-level showing='visible'></low-level>

If low-level has code like

this.attr('showing', true)

it should change the parent scope's visible property.

[wclr]

Justin, your test passes only because parent and child components have the same name for the attribute

<my-toggler visible="visible">

if you replace "visible" attr in child for example with "shown", something like:

<my-toggler shown="visible">

two way binding won't work as it will try to change "shown" attribute in parent, not "visible".

Here is fiddle
http://jsfiddle.net/xKc3H/249/

[wclr]

End there is another problem with two way binding if you try to bind "complex" properties:

<my-toggler shown="visibility.visible">

propertyDataFromScope.parent for "visibility.visible" is not parent scope, but visibility map.

[justinbmeyer]

A fiddle would not show this breaking because this is fixed for 2.0.1. Have you tried it with that code?

[wclr]

Yes I tried it in my project, I updated can.js yesterday from master. I had to change some code to fix this behaviour. Where there any fixes for this?

[wclr]

Would you confirm that this doesn't work? If yes, it is quite severe, issue should be opened and fixed for 2.0.1, I think.