Ability to configure format of pagy_url_for

[joelzwarrington]

pagy/gem/lib/pagy/url_helpers.rb

Line 9 in d70e443

def pagy_url_for(pagy, page, absolute: false, fragment: nil, **_)

I am trying to use Pagy with Turbo Streams and am not able to use pagy_url_for because it doesn't allow the format to be set to :turbo_stream. Thus sending + receiving HTML which doesn't update the page.

As a work-around I am simply doing the following:

pagy_keyset(@posts, request_path: posts_path(format: :turbo_stream))

however, I do need to add all of the params to this url helper if I'd like it passed through (such as when implementing filters)

[ddnexus]

Could you give me some example of the final url strings that you want to get?

[benkoshy]

Avoid XY problem(s)

• You might not need to override pagy_url_for. It's pretty low-level, depending on what you are attempting to accomplish, you may be able to avoid that entirely.
• I have never understood the need for request_path, but if you document your full use-case someone may be able to comment.

Potential Ideas:

Check out this approach which uses turbo_streams, except in the context of infinite scroll:

GET Requests

• benkoshy/pagy_keyset_infinite@029d22a

or you could adopt the following:

<%== pagy_nav(@pagy, anchor_string: 'data-turbo-stream="true"') %>

and that should preserve the params in the browser and also pass it to the rails controller in subsequent requests.

(You might need a later version of hotwire/turbo - because there was a PR which allowed for streaming via get requests.)

POST requests

• Use the links to trigger javascript to submit a form.
• https://benkoshy.github.io/2019/10/09/paginating-search-results-with-a-post-request.html - this may give you some ideas. Warning, I wrote this a long time ago, please use your judgment

[joelzwarrington]

@benkoshy I have exactly what you have using the lazy-loaded turbo frames & GET requests, but originally was using pagy_keyset_next_url to get the next page which didn't work since it'd request the HTML format by default.

Constructing the url/path manually and specifying the format as you have done is what I did to fix the issue.

[benkoshy]

If all is solved I will close the discussion. pls feel free to re-open for any reason if required.