Rails%203%20In%20Action

Pagination
Alright, so that one’s passing. Let’s see what happens when you run rake cucumber:ok
spec again:
66 scenarios (66 passed)
756 steps (756 passed)
# and
72 examples, 0 failures, 19 pending
All areas where you need pagination are working. You’ve called the per method twice,
once in the show action of the ProjectsController and again in the search method
of TicketsController. If you wish to change the number of elements returned for a
list of tickets, you’d need to change both of these locations. Instead, you’ll move the
setting for the number of ticket objects returned on each page into the model.
CLEANING UP AFTER YOURSELF
Let’s take the per(50) call out of this line in the show action of ProjectsController
@tickets = @project.tickets.page(params[:page]).per(50)
turning it into this:
@tickets = @project.tickets.page(params[:page])
Next, you’ll do the same thing for the line that uses per in the search action of the
TicketsController
@tickets = @tickets.page(params[:page]).per(50)
changing it into this:
@tickets = @tickets.page(params[:page])
To make 50 objects the default for this model, you can put this line directly under the
searcher block in your Ticket model:
paginates_per 50
Now when your application is asked for a list of paginated tickets, you’ll be given 50
tickets per page. You can make sure this is the case by rerunning your “Paginating tickets”
feature by running bin/cucumber features/paginating_tickets.feature:
1 scenario (1 passed)
10 steps (10 passed)
Alright, that’s still working, so that’s good! Are your features and specs still working
too? Another quick run of rake cucumber:ok spec will tell you:
66 scenarios (66 passed)
752 steps (752 passed)
# and
72 examples, 0 failures, 19 pending
Great, time to make a commit with this new feature:
git add .
git commit -m "Added pagination for tickets"
git push
441