Class WillPaginate::Collection
In: lib/will_paginate/collection.rb
Parent: Array
ArgumentError InvalidPage Array Collection LinkRenderer Scope ViewHelpers Finder Finder::ClassMethods lib/will_paginate/collection.rb lib/will_paginate/view_helpers.rb ViewHelpers ClassMethods Finder VERSION Deprecation lib/will_paginate/named_scope.rb ClassMethods NamedScope WillPaginate dot/m_8_0.png

The key to pagination

Arrays returned from paginating finds are, in fact, instances of this little class. You may think of WillPaginate::Collection as an ordinary array with some extra properties. Those properties are used by view helpers to generate correct page links.

WillPaginate::Collection also assists in rolling out your own pagination solutions: see create.

If you are writing a library that provides a collection which you would like to conform to this API, you don‘t have to copy these methods over; simply make your plugin/gem dependant on the "will_paginate" gem:

  gem 'will_paginate'
  require 'will_paginate/collection'

  # now use WillPaginate::Collection directly or subclass it

Methods

Attributes

current_page  [R] 
per_page  [R] 
total_entries  [R] 
total_pages  [R] 

Public Class methods

Just like new, but yields the object after instantiation and returns it afterwards. This is very useful for manual pagination:

  @entries = WillPaginate::Collection.create(1, 10) do |pager|
    result = Post.find(:all, :limit => pager.per_page, :offset => pager.offset)
    # inject the result array into the paginated collection:
    pager.replace(result)

    unless pager.total_entries
      # the pager didn't manage to guess the total count, do it manually
      pager.total_entries = Post.count
    end
  end

The possibilities with this are endless. For another example, here is how WillPaginate used to define pagination for Array instances:

  Array.class_eval do
    def paginate(page = 1, per_page = 15)
      WillPaginate::Collection.create(page, per_page, size) do |pager|
        pager.replace self[pager.offset, pager.per_page].to_a
      end
    end
  end

The Array#paginate API has since then changed, but this still serves as a fine example of WillPaginate::Collection usage.

[Source]

    # File lib/will_paginate/collection.rb, line 85
85:     def self.create(page, per_page, total = nil, &block)
86:       pager = new(page, per_page, total)
87:       yield pager
88:       pager
89:     end

Arguments to the constructor are the current page number, per-page limit and the total number of entries. The last argument is optional because it is best to do lazy counting; in other words, count conditionally after populating the collection using the replace method.

[Source]

    # File lib/will_paginate/collection.rb, line 49
49:     def initialize(page, per_page, total = nil)
50:       @current_page = page.to_i
51:       raise InvalidPage.new(page, @current_page) if @current_page < 1
52:       @per_page = per_page.to_i
53:       raise ArgumentError, "`per_page` setting cannot be less than 1 (#{@per_page} given)" if @per_page < 1
54:       
55:       self.total_entries = total if total
56:     end

Public Instance methods

current_page + 1 or nil if there is no next page

[Source]

     # File lib/will_paginate/collection.rb, line 112
112:     def next_page
113:       current_page < total_pages ? (current_page + 1) : nil
114:     end

Current offset of the paginated collection. If we‘re on the first page, it is always 0. If we‘re on the 2nd page and there are 30 entries per page, the offset is 30. This property is useful if you want to render ordinals besides your records: simply start with offset + 1.

[Source]

     # File lib/will_paginate/collection.rb, line 102
102:     def offset
103:       (current_page - 1) * per_page
104:     end

Helper method that is true when someone tries to fetch a page with a larger number than the last page. Can be used in combination with flashes and redirecting.

[Source]

    # File lib/will_paginate/collection.rb, line 94
94:     def out_of_bounds?
95:       current_page > total_pages
96:     end

current_page - 1 or nil if there is no previous page

[Source]

     # File lib/will_paginate/collection.rb, line 107
107:     def previous_page
108:       current_page > 1 ? (current_page - 1) : nil
109:     end

This is a magic wrapper for the original Array#replace method. It serves for populating the paginated collection after initialization.

Why magic? Because it tries to guess the total number of entries judging by the size of given array. If it is shorter than per_page limit, then we know we‘re on the last page. This trick is very useful for avoiding unnecessary hits to the database to do the counting after we fetched the data for the current page.

However, after using replace you should always test the value of total_entries and set it to a proper value if it‘s nil. See the example in create.

[Source]

     # File lib/will_paginate/collection.rb, line 133
133:     def replace(array)
134:       result = super
135:       
136:       # The collection is shorter then page limit? Rejoice, because
137:       # then we know that we are on the last page!
138:       if total_entries.nil? and length < per_page and (current_page == 1 or length > 0)
139:         self.total_entries = offset + length
140:       end
141: 
142:       result
143:     end

[Source]

     # File lib/will_paginate/collection.rb, line 116
116:     def total_entries=(number)
117:       @total_entries = number.to_i
118:       @total_pages   = (@total_entries / per_page.to_f).ceil
119:     end

[Validate]