# How To

This page contains the practical tips and examples to get the job done with Pagy.

You can also Ask any question to the Pagy trained AI for instant answers not covered in this page.

AI-powered answer

You can control the items per page with the limit variable. (Default 20)

You can set its default in the pagy.rb initializer (see How to configure pagy). For example:

Pagy::DEFAULT[:limit] = 25

You can also pass it as an instance variable to the Pagy.new method or to the pagy controller method:

@pagy, @records = pagy(Product.all, limit: 30)

# the limit used in the query will be 10
@pagy, @products = pagy(Product.limit(5), limit: 10)

See also a couple of extras that handle the :limit in some special way:

• gearbox: Automatically change the limit per page depending on the page number
• limit: Allow the client to request a custom :limit (i.e. records per page) with an optional selector UI

You can control the number and position of the page links in the navigation through the :size variable or override the series method.

# size < 7
pagy = Pagy.new(count: 1000, page: 10, size: 5)
pagy.series
#=> [8, 9, "10", 11, 12]
pagy = Pagy.new(count: 1000, page: 2, size: 5)
pagy.series
#=> [1, "2", 3, 4, 5]
pagy = Pagy.new(count: 1000, page: 99, size: 5)
pagy.series
#=> [96, 97, 98, "99", 100] 

# size >= 7 (first, last and gap added)
pagy = Pagy.new(count: 1000, page: 10, size: 7)
pagy.series
#=> [1, :gap 9, "10", 11, :gap, 100]
pagy = Pagy.new(count: 1000, page: 2, size: 7)
pagy.series
#=> [1, "2", 3, 4, 5, :gap, 100]
pagy = Pagy.new(count: 1000, page: 99, size: 7)
pagy.series
#=> [1, :gap, 96, 97, 98, "99", 100] 

# size >= 7; ends: false (no ends added)
pagy = Pagy.new(count: 1000, page: 10, size: 7, ends: false)
pagy.series
#=> [7, 8, 9, "10", 11, 12, 13]
pagy = Pagy.new(count: 1000, page: 2, size: 7, ends: false)
pagy.series
#=> [1, "2", 3, 4, 5, 6, 7]
pagy = Pagy.new(count: 1000, page: 99, size: 7, ends: false)
pagy.series
#=> [94, 95, 96, 97, 98, "99", 100]

pagy = Pagy.new count: 1000, size: 0 # etc
pagy.series
#=> []

You don't need to explicitly pass the page number to the pagy method, because it is pulled in by the pagy_get_page (which is called internally by the pagy method). However you can force a page number by just passing it to the pagy method. For example:

@pagy, @records = pagy(my_scope, page: 3) # force page #3

That will explicitly set the :page variable, overriding the default behavior (which pulls the page number from the params[:page] by default).

Pagy composes its output strings using standard i18n dictionaries. That can be used to change the language and customize your specific app.

# :one_other pluralization (see https://github.com/ddnexus/pagy/blob/master/gem/lib/pagy/i18n.rb)
en:
  pagy:
    aria_label:
      nav:
        one: "Page"
        other: "Pages"
      prev: "Previous"
      next: "Next"
    prev: "<"
    next: ">"
    gap: "…"
    item_name:
      one: "item"
      other: "items"
    info:
      no_items: "No %{item_name} found"
      single_page: "Displaying %{count} %{item_name}"
      multiple_pages: "Displaying %{item_name} %{from}-%{to} of %{count} in total"
    combo_nav_js: "Page %{page_input} of %{pages}"
    limit_selector_js: "Show %{limit_input} %{item_name} per page"

If you are ok with the default supported locale dictionaries just refer to Pagy::I18n.

If you want to customize the translations or some specific output, you should edit the relevant entries in the pagy dictionary.

If you explicitly use the i18n extra, override the pagy target entries in your own custom dictionary (refer to the I18n official documentation).

If you don't use the above extra (and rely on the pagy faster code) you can copy and edit the dictionary files that your app uses and configure pagy to use them.

# load the "en" and "de" locale defined in the custom files at :filepath:
Pagy::I18n.load({ locale: 'de', filepath: 'path/to/my-custom-de.yml' },
                { locale: 'en', filepath: 'path/to/my-custom-en.yml' })

You can customize the aria-label attributes of all the pagy helpers by passing the :aria_label string ( See pagy_nav)

You can also replace the pagy.aria_label.nav strings in the dictionary, as well as the pagy.aria_label.prev and the pagy.aria_label.next.

See more details in the ARIA attributes Page.

Pagy uses the :page_param variable to determine the param it should get the page number from and create the URL for. Its default is set as Pagy::DEFAULT[:page_param] = :page, hence it will get the page number from the params[:page] and will create page URLs like ./?page=3 by default.

You may want to customize that, for example to make it more readable in your language, or because you need to paginate different collections in the same action. Depending on the scope of the customization, you have a couple of options:

1. Pagy::DEFAULT[:page_param] = :custom_param will be used as the global default
2. pagy(collection, page_param: :custom_param) or Pagy.new(count:100, page_param: :custom_param) will be used for a single instance (overriding the global default)

You can also override the pagy_get_page if you need some special way to get the page number.

If you need to customize some HTML attribute of the page links, you may not need to override the pagy_nav* helper. It might be enough to pass some extra attribute string with the :anchor_string keyword argument. For example:

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

See more advanced details about The anchor_string argument

When you need to add some custom param or alter the params embedded in the URLs of the page links, you can set the variable :params to a Hash of params to add to the URL, or a Proc that can edit/add/delete the request params.

If it is a Proc it will receive the key-stringified params hash complete with the page param and it should return a possibly modified version of it.

An example using except and merge!:

@pagy, @records = pagy(collection, params: ->(params) { params.except('not_useful').merge!('custom' => 'useful') })

You can also use the :fragment keyword argument to add a fragment to the URLs of the pages:

<%== pagy_nav(@pagy, fragment: '#your-fragment') %>

When you need something more radical with the URL than just massaging the params, you should override the pagy_url_for right in your helper.

[!!!warning Override pagy_trim if using Trim Extra

If you are also using the trim extra you should also override the pagy_trim method or the Pagy.trim javascript function.

def pagy_url_for(pagy, page, absolute: false)
  params = request.query_parameters.merge(pagy.vars[:page_param] => page, only_path: !absolute)
  url_for(params)
end

def pagy_url_for(_pagy, page, **_)
  page
end

The pagy_info and the pagy_limit_selector_js helpers use the "item"/"items" generic name in their output. You can change that by editing the values of the "pagy.item_name" i18n key in the dictionary files that your app is using.

Besides you can also pass the :item_name by passing an already pluralized string directly to the helper call:

<%== pagy_info(@pagy, item_name: t(`activerecord.model.product`, count: @pagy.count) %>
<%== pagy_limit_selector_js(@pagy, item_name: t('activerecord.model.product', count: @pagy.limit) %>

For all its own interactive helpers the pagy gem includes a few stylesheets that you can customize.

Besides that, pagy provides a few frontend extras for bootstrap, bulma and tailwind that come with a decent styling provided by their respective framework.

If you need to further customize the styles provided by the extras, you don't necessary need to override the helpers in most of them: here are a few alternatives:

• Check whether the specific extra offers customization (e.g. bulma)
• Define the CSS styles to apply to the pagy CSS classes
• If sass/scss is available: extend the pagy CSS classes with some framework defined class, using the @extend sass/scss directive
• Use the jQuery addClass method
• Use a couple of lines of plain javascript

In order to get a decent default look, a couple of helpers (i.e. pagy*_combo_nav_js, pagy_limit_selector_js) assign element style attributes to one or more tags. You can override their rules in your own stylesheets by using the attribute [style] selector and !important. Here is an example for overriding the width of the input element:

.pagy input[style] {
  /* This is just for the sake of demo: indeed the width is already calculated and assigned dynamically 
     considering the total number of digits that may appear in the input, so you should not need to override it */
  width: 5rem !important;
}

You include the pagy modules in your controllers and helpers, so if you want to override any of them, you can redefine them right in your code, where you included them.

You can read more details in the nice How to Override pagy methods only in specific circumstances mini-post by Ben Koshy.

Also, consider that you can use prepend if you need to do it globally:

module MyOverridingModule
  def pagy_any_method
    #...
    super
    #...
  end
end
Pagy::Backend.prepend MyOverridingModule
# and/or
Pagy::Frontend.prepend MyOverridingModule

# e.g. applicaton_controller.rb
def pagy_get_count(collection, vars)
  collection.respond_to?(:count_documents) ? collection.count_documents : super
end

See the array extra.

Pagy works out of the box with ActiveRecord collections, however here are a few specific cases that might be treated differently:

@pagy, records     = pagy(Post.all)
@decorated_records = records.decorate # or YourDecorator.method(records) whatever works

# Passing the right arguments to the internal `collection.count(...)` (See the ActiveRecord documentation for details)
@pagy, @records = pagy(custom_scope, count_args: [:join])

# or directly pass the right count to pagy (that will directly use it skipping its own `collection.count(:all)`)
@pagy, @records = pagy(custom_scope, count: custom_count)

q              = Person.ransack(params[:q])
@pagy, @people = pagy(q.result)

When your app is a service that doesn't need to serve any UI, but provides an API to some sort of client, you can serve the pagination metadata as HTTP headers added to your response.

In that case you don't need the Pagy::Frontend nor any frontend extra. You may not even need the standard pagination, but use the Pagy::Keyset pagination. Anyway you may want to use the headers extra and use its helpers to add the headers to your responses, and other useful backend extras like the limit extra and the jsonapi extra.

See the jsonapi extra.

If your app uses ruby as pure backend and some javascript frameworks as the frontend (e.g. Vue.js, react.js, ...), then you may want to generate the whole pagination UI directly in javascript (with your own code or using some available javascript module).

In that case you don't need the Pagy::Frontend nor any frontend extra. You should only require the metadata extra and pass the pagination metadata in your JSON response.

Pagy has a few extras dedicated to gems returning search results:

• elasticsearch_rails
• searchkick
• meilisearch

With particular requirements/environment an id-based pagination might work better than a classical offset-based pagination, You can use an interesting approach proposed here.

Use the calendar extra that adds pagination filtering by calendar time unit (year, quarter, month, week, day).

By default pagy tries to derive parameters and variables from the request and the collection, so you don't have to explicitly pass it to the pagy* method. That is very handy, but assumes you are paginating a single collection per request.

When you need to paginate multiple collections in a single request, you need to explicitly differentiate the pagination objects. You have the following common ways to do so:

# dashboard_controller
def index
  @pagy_foos, @foos = pagy(Foo.all, request_path: '/foos')
  @pagy_bars, @bars = pagy(Bar.all, request_path: '/bars')
end

<-- /dashboard.html.erb -->
<%== pagy_nav(@pagy_foos) %>
<%== pagy_nav(@pagy_bars) %>
<-- Pagination links of `/foos?page=2` instead of `/dashboard?page=2` -->
<-- Pagination links of `/bars?page=2` etc. -->
<-- Success -->

# dashboard_controller
def index
  @pagy_foos, @foos = pagy(Foo.all)
  @pagy_bars, @bars = pagy(Bars.all)
end

<-- /dashboard.html.erb -->
<% turbo_frame "foos" do %>
<%== pagy_nav(@pagy_foos) %>
<% end%>
<% turbo_frame "bars" do %>
<%== pagy_nav(@pagy_bars) %>
<% end%>
<-- Pagination links will be `/dashboard?page=2` -->
<-- We don't want that! -->

  <-- movies/index.html.erb -->
  
  <-- movies#bad_movies -->
  <%= turbo_frame_tag "bad_movies", src: bad_movies_path do %>    
      <%= render "movies_table", locals: {movies: @movies}%>
      <%== pagy_bootstrap_nav(@pagy) %>    
  <% end %>

  <-- movies#good_movies -->
  <%= turbo_frame_tag "good_movies", src: good_movies_path  do %>    
      <%= render "movies_table", locals: {movies: @movies}%>
      <%== pagy_bootstrap_nav(@pagy) %>    
  <% end %>   

  # controller action 
def good
  @pagy, @movies = pagy(Movie.good, limit: 5)
end

def bad
  @pagy, @movies = pagy(Movie.bad, limit: 5)
end 

def index # controller action
  @pagy_stars, @stars     = pagy(Star.all, page_param: :page_stars)
  @pagy_nebulae, @nebulae = pagy(Nebula.all, page_param: :page_nebulae)
end

You can easily wrap your existing pagination with the pagy_calendar method. Here are a few examples adding :year and :month to different existing statements.

# pagy without calendar
@pagy, @record = pagy(collection, any_vars: value, ...)
# wrapped with pagy_calendar
@calendar, @pagy, @records = pagy_calendar(collection,
                                           year:  {},
                                           month: {},
                                           pagy:  { any_vars: value, ... })

# any other backend constructors (e.g. pagy_searchkick)
@pagy, @record = pagy_searchkick(pagy_search_args, any_vars: value, ...)
# wrapped with pagy_calendar
@calendar, @pagy, @records = pagy_calendar(pagy_search_args,
                                           year:  {},
                                           month: {},
                                           pagy:  { backend:  :pagy_searchkick,
                                                    any_vars: value, ... })

Then follow the calendar extra documentation for more details.

In order to limit the pagination to a maximum number of pages, you can pass the :max_pages variable.

For example:

@pagy, @records = pagy(collection, max_pages: 50, limit: 20)
@records.size #=> 20   
@pagy.count #=> 10_000
@pagy.last #=> 50

@pagy, @records = pagy(collection, max_pages: 50, limit: 20, page: 51)
#=> Pagy::OverflowError: expected :page in 1..50; got 51

If the @pagy.count in the example is 10_000, the pages served without :max_pages would be 500, but with :max_pages: 50 pagy would serve only the first 50 pages of your collection.

That works at the Pagy/Pagy::Countless level, so it works with any combination of collection/extra, including limit, gearbox and search extras, however it makes no sense in Pagy::Calendar unit objects (which ignore it).

With the other pagination gems you cannot paginate a subset of a collection that you got using offset and limit. With Pagy it is as simple as just adding the :outset variable, set to the initial offset. For example:

subset                   = Product.offset(100).limit(315)
@pagy, @paginated_subset = pagy(subset, outset: 100)

Assuming the :limit default of 20, you will get the pages with the records you are expecting. The first page from record 101 to 120 of the main collection, and the last page from 401 to 415 of the main collection. Besides the from and to attribute readers will correctly return the numbers relative to the subset that you are paginating, i.e. from 1 to 20 for the first page and from 301 to 315 for the last page.

The pagy_get_count method works out of the box with ActiveRecord collections; for other collections (e.g. mongoid, etc.) you might want to change the :count_args default to suite your ORM count method:

Pagy::DEFAULT[:count_args] = []

or in extreme cases you may need to override it in your controller.

When your collection is already paginated and contains count and pagination metadata, you don't need any pagy* controller method. For example this is a Tmdb API search result object, but you can apply the same principle to any other type of collection metadata:

#<Tmdb::Result page=1, total_pages=23, total_results=446, results=[#<Tmdb::Movie ..>,#<Tmdb::Movie...>,...]...>

As you can see, it contains the pagination metadata that you can use to setup the pagination with pagy:

# get the paginated collection
tobj = Tmdb::Search.movie("Harry Potter", page: params[:page])
# use its count and page to initialize the @pagy object
@pagy = Pagy.new(count: tobj.total_results, page: tobj.page)
# set the paginated collection records
@movies = tobj.results

Pagy doesn't need to know anything about the kind of collection you paginate. It can paginate any collection, because every collection knows its count and has a way to extract a chunk of items given a start/offset and a per-page/limit. It does not matter if it is an Array or an ActiveRecord scope or something else: the simple mechanism is the same:

1. Create a Pagy object using the count of the collection to paginate
2. Get the page of items from the collection using the start/offset and the per-page/limit (pagy.offset and pagy.limit)

Here is an example with an array. (Please, notice that this is only a convenient example, but you should use the array extra to paginate arrays).

# paginate an array
arr = (1..1000).to_a

# Create a Pagy object using the count of the collection to paginate
pagy = Pagy.new(count: arr.count, page: 2)
#=> #<Pagy:0x000055e39d8feef0 ... >

# Get the page using `pagy.offset` and `pagy.limit`
paginated = arr[pagy.offset, pagy.limit]
#=> [21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40]

This is basically what the pagy method included in your controller does for you in one go:

@pagy, @products = pagy(Product.some_scope)

Then of course, regardless the kind of collection, you can render the navigation links in your view:

<%== pagy_nav(@pagy) %>

See the Pagy::Backend API documentation for more details.

These helpers take the Pagy object and return the HTML string with the pagination links, which are wrapped in a nav tag and are ready to use in your view. For example:

<%== pagy_nav(@pagy) %>

Unlike other gems, Pagy does not decide for you that the nav of a single page of results must not be rendered. You may want it rendered... or maybe you don't. If you don't... wrap it in a condition and use the pagy_nav* only if @pagy.pages > 1 is true. For example:

<%== pagy_nav(@pagy) if @pagy.pages > 1 %>

By default Pagy generates all the page links including the page param. If you want to remove the page=1 param from the first page link, just require the trim extra.

Every pagination gem needs the collection count in order to calculate all the other variables involved in the pagination. If you use a storage system like any SQL DB, there is no way to paginate and provide a full nav system without executing an extra query to get the collection count. That is usually not a problem if your DB is well organized and maintained, but that may not be always the case.

Sometimes you may have to deal with not very efficient legacy apps/DBs that you cannot totally control. In that case the extra count query may affect the performance of the app quite badly.

You have 2 possible solutions in order to improve the performance.

# override the pagy_get_count method adding
# the Rails.cache wrapper around the count call
def pagy_get_count(collection, _vars)
  cache_key = "pagy-#{collection.model.name}:#{collection.to_sql}"
  Rails.cache.fetch(cache_key, expires_in: 20 * 60) do
    collection.count(:all)
  end
end

# reset the cache when the model changes (you may omit the callbacks if your DB is static)
after_create { Rails.cache.delete_matched /^pagy-#{self.class.name}:/ }
after_destroy { Rails.cache.delete_matched /^pagy-#{self.class.name}:/ }

Here are some tips that will help choosing the best way to use Pagy, depending on your requirements and environment.

Pagy output html safe HTML, however, being an agnostic pagination gem it does not use the specific html_safe rails helper on its output. That is noted by the Brakeman gem, that will raise a warning.

You can avoid the warning adding it to the brakeman.ignore file. More details here and here.

Pass an overflowing :page number and Pagy will raise a Pagy::OverflowError exception.

This often happens because users/clients paginate over the end of the record set or records go deleted and a user went to a stale page.

You can handle the exception by using the overflow extra which provides a few easy and ready to use solutions for a few common cases, or you can rescue the exception manually and do whatever fits you better.

Here are a few options for manually handling the error in apps:

• Do nothing and let the page render a 500
• Rescue and render a 404
• Rescue and redirect to the last known page (Notice: the overflow extra provides the same behavior without redirecting)

rescue_from Pagy::OverflowError, with: :redirect_to_last_page

private

def redirect_to_last_page(exception)
  redirect_to url_for(page: exception.pagy.last), notice: "Page ##{params[:page]} is overflowing. Showing page #{exception.pagy.last} instead."
end

• Pagy has 100% test coverage.
• You only need to test pagy if you have overridden methods.

If you need to test pagination, remember:

• Pagy::DEFAULT should be set by your initializer and be frozen. You can test that your code cannot change it.
• You can override defaults - i.e. any pagy variable can be passed to a pagy constructor. For example:

@pagy, @books = pagy(Book.all, limit: 10) # the default limit has been overridden

If you really need to use your own templates, you absolutely can. Here is a static example that doesn't use any other helper nor dictionary file for the sake of simplicity, however feel free to add your dynamic variables and use any helper and dictionary entries as you need:

<%# IMPORTANT: use '<%== ... ' instead of '<%= ... ' if you run this in rails %>

<%# The a variable below is set to a lambda that generates the a tag %>
<%# Usage: a_tag = a.(page_number, text, classes: nil, aria_label: nil) %>
<% a = pagy_anchor(pagy) %>
<nav class="pagy nav" aria-label="Pages">
  <%# Previous page link %>
  <% if pagy.prev %>
    <%= a.(pagy.prev, '&lt;', aria_label: 'Previous') %>
  <% else %>
    <a role="link" aria-disabled="true" aria-label="Previous">&lt;</a>
  <% end %>
  <%# Page links (series example: [1, :gap, 7, 8, "9", 10, 11, :gap, 36]) %>
  <% pagy.series.each do |item| %>
    <% if item.is_a?(Integer) %>
      <%= a.(item) %>
    <% elsif item.is_a?(String) %>
      <a role="link" aria-disabled="true" aria-current="page" class="current"><%= item %></a>
    <% elsif item == :gap %>
      <a role="link" aria-disabled="true" class="gap">&hellip;</a>
    <% end %>
  <% end %>
  <%# Next page link %>
  <% if pagy.next %>
    <%= a.(pagy.next, '&gt;', aria_label: 'Next') %>
  <% else %>
    <a role="link" aria-disabled="true" aria-label="Next">&lt;</a>
  <% end %>
</nav>

You can use it as usual: just remember to pass the :pagy local set to the @pagy object:

<%== render file: 'nav.html.erb', locals: {pagy: @pagy} %>

pagy demo
# or: bundle exec pagy demo

You may want to read also the Pagy::Frontend API documentation for complete control over your templates.