The paramAttributes values are not interpolated

[bpierre]

See http://jsfiddle.net/aB577/

[yyx990803]

paramAttributes is intended for simple inline data only, so the attribute value will be interpreted as raw values instead of a binding. A child component can already access parent data directly in the template, and to actually share data you should use v-with.

[bpierre]

I see. I built a better example, just to see if I missed an obvious solution for my case.

Basically, I have a component, and I’d like to bind it to a data property in the parent VM. The parent’s VM already has a property which is directly on data, so I cannot directly use v-with.

Ideally, I’d like to bind the data.value of my component to the data.appValue of my app, the same way I can bind an input’s value to a data property with v-model.

• Here is the first version of the base demo (not working): http://jsfiddle.net/3at6y/
• With v-with (using $watch to sync the two properties): http://jsfiddle.net/YmwH3/
• With events (just for the sake of completeness): http://jsfiddle.net/Vap6m/
• With v-ref and $watch: http://jsfiddle.net/Wvy7z/
• And finally, a version with a (quick & dirty) v-bind directive, in order to synchronize the two data properties without adding any code: http://jsfiddle.net/r2SFu/

I like the last one, because the data structures are kept separated, like with a <input v-model="appValue">.

What do you think?

[yyx990803]

Thanks for the detailed examples! That totally make sense. I think something like your v-bind could be indeed useful. It also makes me think about some lock mechanism to prevent values from circular triggering.

[yyx990803]

1a05dea