Pagy v43 calendar pagination to automatically show last page

[bellenss]

In Pavy V43 page_ keys are no longer to be explicitly set. Using calendar sorting, by default the olders pagination result is shown. How can I show the most recent entries by default?
I used to set params[month_page] to the current month, which is now no longer working in V43

[ddnexus]

Do you mean setting the order: :desc option for the unit config?

The collection should also be ordered accordingly.

[bellenss]

not quite. For the year this works, as I'm using a dropdown for year selection. But month-wise, this inverses the pill pagination, with december left and january right. Which is not what I want. The month order should stay, but december (or the latest month) should be selected by default.

[ddnexus]

I used to set params[month_page] to the current month

Wasn't setting the params[month_page] already ignored in v9? That's how pagy produces the links for different units... Could you share the code that was working in v9?

The month order should stay, but december (or the latest month) should be selected by default.

That's a odd behavior for pagination. I don't remember to have thought about that possibility, so I have no idea how to do it ATM.

[bellenss]

params[:month_page] ||= Time.zone.today.month.to_s
@calendar, @pagy, @rekeningen = pagy_calendar(query, year: {}, month: {}, pagy: {})

is working just fine in v9.4.0

In a calendar pagination, I believe having the most recent view first makes a lot of sense. Think about meetings (as in your calendar APP), invoices, ... without necessarily having to reverse the order.

[ddnexus]

Ok, so you are just setting the page default, which was nil before, and 1 now (IIRC)... which is likely the reason ||= never works. Easy to update, right?

Anyway setting the page month that way is really fragile because it actually selects the page of the last month only if your app shows only records of the current year. What if you paginate the records of last year while the current month is May for example?

[bellenss]

Not really, as the param[:month_page] setting in my controller has no effect anymore in V43. I guess the parameters in Pagy are now read directly from the request? I try to set it at whatever value, but it has no impact on the active page.

[ddnexus]

Well... you need to debug and find where it sets it... I don't remember it and I cannot do that ATM.

[ddnexus]

Just got a min to think to this again...

Yes, pagy reads from the client request, not from the rails params: if there's no param, then page 1 is the default value used.

If you really want to force the unit page, you should override this line:

pagy/gem/lib/pagy/classes/calendar/calendar.rb

Line 79 in e966efe

conf[unit][:page] = @params["#{unit}_#{@page_key}"] # requested page

changing = with ||=, then you can force the page passing page: your_default as an option to the unit option hash.

It's not pretty, but neither is defaulting to the last page 🤭 ... however it should work your way.

[bellenss]

I'm expanding my use case to provide year_page and month_page parameters in the URL. As such, browser URL behavior is consistent and in line with pagy. So far, this looks to be all working out well. I'll need some more time to finish. I'll report back here when ready. This is not a high-prio topic for me, so might take some time. Thanks for the support so far!

[ddnexus]

BTW, generalizing the default to the last page is tricky, because you need to know the collection count in order to calculate it. If your special case can calculate it using just today, it will work with the override.

Since it will be for all filters, the simplest alternative would be just reversing the order, and avoid overriding. It would also look more natural and easy to understand to me.

[bellenss]

Just as a short write-up on how I updated my use case.
Migration issue:

• pagy V43 reads the URL parameters directly from the request, and setting / overwriting them in the Rails controller no longer works.

I have updated my use-case to reflect the actual params (month_page and year_page in my situation) in the URL. When they are not present, I set them in my controller and trigger a redirect (yes, I know, this is a performance penalty).

The benefit is that the parameters are now present in the URL, and the user can navigate them.

@calendar, @pagy, @rekeningen = pagy(:calendar, query, year: { order: :desc }, month: { })

if @calendar && (params[:year_page].blank? || params[:month_page].blank?)
  year_page = params[:year_page] || cookies[:year_page] || 1
  month_page = params[:month_page] || cookies[:month_page] || (year_page == 1 ? @calendar[:month].last : 1)
  redirect_to url_for(params.permit!.to_h.merge(year_page: year_page, month_page: month_page))
  return
end

Thanks for the support! Love using pagy in my Rails app 👍