Pagination not reset after changing points about easy-search-leaderboard

[matteodem]

Yes it is intended. From a UX view it's a bad thing if search results are changed without "apparent" reason for the users that didn't do the action that caused the change. It's even bad that it does resort at the moment, but that's Meteor's default way of staying reactive and it'd need some hacks to go around that.

[Urigo]

I see and understand the approach. that's right for search results.

I also can't help but thinking how similar is your solution to just regular sorting+filtering+pagination, let's say activity log or news feed.
In those cases we would want that it will be reactive.
I think it would be a shame to use a completely different library there (like meteor-pages ) and not adjust your library to do the same.
What are your thoughts on that?

[matteodem]

I am not talking about any app-specific things, it's a general UX, user perspective view where some content suddenly vanishes and the user is confused and maybe leaves the app. One might think it's normal but in a way it isn't. That's why Disqus and Youtube use the "load more comments" approach. Hope it's understandable explained.

I had a look at a lot of different pagination packages, but those weren't easily useable with Easy-Search and it's architecture. One could use subscription based search like here in a Meteor App and achieve your desired result that way: https://github.com/matteodem/meteor-easy-search/blob/master/lib/easy-search-common.js#L49. Simply use the Pagination collection instead of a normal one inside your app.

[matteodem]

Please let me know how this works.