Filters ng-repeat not working inside vs-repeat about angular-vs-repeat

[kamilkp]

That's entirely not the fault of vs-repeat. The problem is that vs-repeat creates new non-isolated scope. And if you write:

<div ng-repeat="item in filtered = (items | filter:MyFilter | filter:query )">

you basically write to a filtered variable on the current scope. If you wrap it with vs-repeat the filtered variable gets written into vs-repeat's scope not the outer scope. Writing like that:

<div ng-repeat="item in filtered.result = (items | filter:MyFilter | filter:query )">

should fix the issue. Chceck out the updated gist: https://gist.github.com/kamilkp/40332795f8cf256772ce/revisions

I didn't test it but i'm pretty sure it will work like that.

[kamilkp]

Yes, filters are not supported yet. Also this syntax:

<div ng-repeat="{key, value} in someObject">

is not supported yet.
Supporting filters is relatively easy to implement so i'll try to do it by the end of the week.

[tcdevs]

That would be great!

[kamilkp]

Try it now (pull latest commit from master). Filters should be working now.

[tcdevs]

Kamilkp it works like a charm, just tested it with multiple filters. 😉 Thanks for the help!

[tcdevs]

Your directive is best solution (imo) for data with 200+ items, instead of pagenation or (fullpage) inifinity scroll.

[tcdevs]

I noticed that this type of filtering syntax is not working:
<div ng-repeat="item in filtered = (items | filter:MyFilter | filter:query )">
This is useful to get the total length of the filtered items.

[kamilkp]

Well, that's odd since my regex produces the exact same output as the regex in the original ngRepeat directive. Can you make a jsfiddle with an example?

[tcdevs]

I had problems with jsFiddle so i made a gist with single html file example. Both with a normal ng-repeat and vs-repeat. You can check it here: https://gist.github.com/tcdevs/b53858b2df776ce9f3ff

When you run the example you see that the applied filters and filtered1 model work correctly but the filtered2 model not.

[tcdevs]

I did test it and you are once again correct. Nice trick to use the ng-init attribute! That's one of the ng-attributes i never actually use, but in this case its handy.

Thanks again for the quick help!