v-model and v-on="input"

[paglias]

It looks like that the input event callback defined in a v-on directive is executed before the v-model directive updates the viewmodel.

http://jsfiddle.net/8FUdD/1/ if you give a look at the console it will be logging the old value

It would be nice to have a v-change directive like angular's ngChange http://docs.angularjs.org/api/ng/directive/ngChange that relies on a watcher on the ngModel instead of an event.

[yyx990803]

Hmm if you have a component for the v-repeat instances you can use a $watch watcher to save. Or in this specific case, just save in a setTimeout(0) would also work. I'll think about if there's an even easier way.

[yyx990803]

Haha, I found out it's actually because I'm compiling directives backwards with while (i--) instead of a for loop, so the directives that comes after gets compiled first. I've reversed the order to make the compile order consistent with the order they appear in the markup.