alethes / meteor-pages

Meteor pagination
MIT License
403 stars 84 forks source link

Filters issue (pages.set({filters: [Object]|}) = result 0. #198

Open master7xx opened 8 years ago

master7xx commented 8 years ago
var zz = {}
> pages.filters
Object {categoryId: "14279"}
> zz = pages.filters
Object {categoryId: "14279"}
>zz.counts = 1
1
>zz
Object {categoryId: "14279", counts: 1}
>pages.set({filters: zz})
0
> pages.filters
Object {categoryId: "14279", counts: 1}

As a result: page not refreshed and nothing changed. Or i miss something, i just want modify filter on fly, add and remove expressions in existing filter.

UPD: Chrome latest (48.0.2564.109 m), Mozilla Firefox (41.0.1).

elliotberry commented 8 years ago

It looks like client-side filtering broke again. Can anyone confirm?

Hizoul commented 8 years ago

Yes I can confirm that client-side Filtering is currently broken. Using Meteor 1.2.1 and alethes:pages @1.8.4 everything is working fine. But using Meteor 1.3.1 and alethes:pages@1.8.6 breaks client-side filtering. On Some collections with very easy filtering it sometimes works, but on another Collection its completely broken. If i don't set any filters then it will show nothing. Setting a Filter will add the newly filtered Items to the list. Changing the Filter again will leave the previously added Items in the List and add the new Items of the new Filter result.

johannbotha commented 8 years ago

+1 client filtering beaks on 1.3.1 but works on 1.2.1