I like the manual approach of looking inside the
pagy object and finding your way to get what you want! That is what I usually do instead of searching the doc :)
A simpler approach that I recommend for Pagy, is searching into the How To, which should give you the official and tested recipes to get what you want.
Skip Single Page Navs
Handle Pagy::OverflowError exceptions
I just realized that the README was lacking those very commonly needed details, and I added them to the example.
Thank you Chris!
Monroe, 3.0 is better than 2.0 and 1.0, obviously :)
Depending on what you used in 2.0, you might be OK even without changing anything in your code, and if you have to change something it will probably be just search and replace, (some method and variable have been renamed). Please, check the CHANGELOG for complete details.
The elasticsearch extras refactoring mentioned by Tabish happened in 2.0, and 3.0 didn't touch it.
Pagy 3.0 is out!
Now ~40x faster, ~36x lighter!
Take a look at the charts ;)
I certainly agree with the "Chris... job well done": indeed I couldn't have explained it better, but let me point out that the Pagy docs does mention it everywhere it makes sense:
The searchkick extra has been refactored in pagy v2.0. If you need more support, please use the gitter chat. Thanks.
Posted in Pagy Frontend Extra MAterialize
Did you add the
gem 'pagy' into the Gemfile?
I couldn't have explained it better - even being the author of Pagy.