How to setup keynav_js with infinite scrolling?

[Splines]

First of all, thanks a lot for this awesome gem ✨ We recently upgraded to v43.

From the docs it's not clear to me how to get keynav_js to work with infinite scrolling. Here is what I did:

When the user clicks on my search button:

• In the Rails controller, obtain paginated search results via @pagy, @records = pagy(:keynav_js, my_search_results, limit: 2).
• Render the @records via TurboStream (here: the first 2 records as dummy example).
  Also render the value of pagy.page_url(:next) in the HTML as data attribute.
• Have a scroll listener set up in JS (Stimulus controller). Whenever the user scrolls further down to it:
  in JS: extract the next pagy url from the HTML data attribute, modify the form to include a page input, and re-request form submission. My controller handles the case where page > 2 separately: it appends via TurboStreams to the now existing list (which already contained the first two results).

Is this how it is supposed to work? I first got a Base64 error due to page_arguments = JSON.parse(B64.urlsafe_decode(page)) in pagy/toolbox/paginators/keynav_js.erb. So I base64-encoded the value of page. Now I get the error undefined method 'shift' for an instance of Integer that I haven't traced down yet.

It seems I'm fundamentally doing something wrong. I'm missing a usage example in the docs. The keyset docs neither include one. But it includes this in the "How it works" section:

You request the next URL, which has the page param set to the cutoff of the current page.

Via pagy.page_url(:next), I get a url like "http://localhost:3000/lectures/search?search%5Bfulltext%5D=&page=2" (*). Are there more arguments needed? What do I have to Base64-encode?

(*) GitHub seems to currently have some problems when displaying HTML entities (quite annoying in pull requests). The URL should end in "page equals 2", not in "ge equals 2"

[Splines]

I've used keyset now and there it seems to work without any problems since the page param is properly base64-encoded there.

[ddnexus]

Yes, keyset is the best tool for the job.

[ddnexus]

From the docs it's not clear to me how to get keynav_js to work with infinite scrolling

That's because keynav_js is designed to to use keyset pagination with numeric page nav helpers, which would normally be impossible. For "infinite scrolling" you use keyset directly.