Equivalent of Pagy.new in v43

[dshorthouse]

I'm using pagy in a Sinatra environment with Elasticsearch in a custom, non-Rails way and just upgraded to v43. Most migrations worked really well thanks to the equivalents posted in the migration README. The one exception is the dozen or so instances of Pagy.new I used for custom handling of total counts, paging, and limits. For example, I have v9 pagy code like this:

@pagy = Pagy.new(count: results[:total][:value], limit: limit, page: page)
@results = results[:hits]

...where results is that returned from my elasticsearch index response using symbolized keys and with the paging activities happening immediately upstream from these lines of code so that I'm merely passing in their values to Pagy.new.

I'm very close to duplicating this same behaviour in v43 by trying this:

@pagy, @results = pagy(:offset, results[:hits], count: results[:total][:value], limit: limit, page: 1)

Note that I have to force the page = 1 here because paging actually happens in my immediate upstream code. This is not entirely desirable because of course the rendered view has its page 1 permanently chosen via the @pagy.series_nav(:bootstrap) I use.

How might I get a functioning replacement for Pagy.new behaviour in v43?

[dshorthouse]

Aha! I finally found the answer to my own question:

@pagy = Pagy::Offset.new(count: results[:total][:value], page: page, limit: limit, request: Pagy::Request.new(request))
@results = results[:hits]

[ddnexus]

Why you don't just do:

@pagy = pagy(:elasticsearch_rails, results)

And BTW, in your example you should pass request: request.

[dshorthouse]

I tried :elasticsearch_rails but my models do not have the requisite Rails search methods for this to work.

[ddnexus]

This does not require any search in the model IIRC, just the results object. Or you mean that you don't use the elasticsearch_rails gem?

[dshorthouse]

That's right, I don't use the elasticsearch_rails gem.

[ddnexus]

Then in that case, I think you are doing it right, including the request: Pagy::Request.new(request)), because it is instantiated in the pagy method that you don't use.