Reverse filters support for v1.0

[karevn]

Continuation of this work: #1441

[yyx990803]

👍 thanks!

[yyx990803]

Unfortunately, had to revert this because this actually neglects a use case where the user attempts to use v-model on a v-for alias with a read-only filter, e.g. orderBy. This is in fact pretty common and is what the original warning is trying to prevent.

With this PR, such use case no longer receives a warning and actually writes the value back to the original array at the wrong index.

[karevn]

Ok. Any ideas for enhancements?
16 нояб. 2015 г. 21:50 пользователь "Evan You" notifications@github.com
написал:

Unfortunately, had to revert this because this actually neglects a use
case where the user attempts to use v-model on a v-for alias with a
read-only filter, e.g. orderBy. This is in fact pretty common and is what
the original warning is trying to prevent.

With this PR, such use case no longer receives a warning and actually
writes the value back to the original array at the wrong index.

—
Reply to this email directly or view it on GitHub
#1818 (comment).

[yyx990803]

I tried working on top of your PR but haven't had a clean solution yet. Will take a deeper look later this week.

[karevn]

I think we should figure out use cases first. :)
16 нояб. 2015 г. 22:05 пользователь "Evan You" notifications@github.com
написал:

I tried working on top of your PR but haven't had a clean solution yet.
Will take a deeper look later this week.

—
Reply to this email directly or view it on GitHub
#1818 (comment).