Hey everyone! We're facing an issue with paginati...
# community-help
m
Hey everyone! We're facing an issue with pagination in our catalog. We're using Next.js with server-side rendering, and our templates are sorted by a
popularity
field. The problem is that since items are re-ranked dynamically, pagination becomes inconsistent – some templates may disappear or reappear as the user navigates between pages. One workaround I thought of is to track all the templates already shown and send them as
hidden_hits
to Typesense. This way, we'd only retrieve new, unseen templates on each page. But this approach isn't ideal, as it adds complexity and increases data transfer. Has anyone run into a similar problem? Are there any well-known patterns or solutions to handle this?
f
You can check out instantsearch's repo as well:https://github.com/algolia/instantsearch/issues
m
What specifically does it do differently?
f
Sorry, I was talking about issue tracking over there as well! This issue is more of rendering / UI rather than our Adapter. Since we don't officially maintain React instantsearch or Next.js' package, I decided to refer you to the official repo