Rails%203%20In%20Action

440 CHAPTER 16 Basic performance enhancements
1 scenario (1 passed)
10 steps (10 passed)
That’s all there is to paginating a resource. You can also call the page and per methods
on models themselves rather than associations; it was just in this case that you
were calling it on an association.
Before you make a commit for this change, quickly make sure that everything’s
working by running rake cucumber:ok spec:
Failing Scenarios:
cucumber features/searching.feature:23
cucumber features/searching.feature:29
cucumber features/searching.feature:35
62 scenarios (3 failed, 59 passed)
736 steps (3 failed, 6 skipped, 727 passed)
Oh dear, it appears the feature in features/searching.feature has been broken by your
changes! Good thing that you’ve got a feature to catch these kinds of things.
FIXING BROKEN SCENARIOS
All three scenarios in this feature failed with the same error:
undefined method 'current_page' for ...
This looks to be associated with the feature you just implemented, as it’s trying to call
a method called current_page. If you look a couple of lines down in the output, you’ll
see that there’s a line in the stack trace that shows that this is from Kaminari:
...kaminari/helpers/action_view_extension.rb:21:in 'paginate'
Okay, so it looks to be a problem coming from Kaminari, but why? Well, if you look
even further down in the stacktrace for this error somewhere in your application,
probably from the app folder, you’ll come across this line:
./app/controllers/tickets_controller.rb:60:in 'search'
What’s so great about this line? Well, this line renders the projects/show view:
render "projects/show"
Above that, however, is the real culprit:
@tickets = @project.tickets.search(params[:search])
You’re not calling either page or per on your search results, and so it’s not going to be
paginating them. You’re going to call the same methods you called back in the
ProjectsController’s show action here so that you get paginated search results:
@tickets = @project.tickets.search(params[:search])
@tickets = @tickets.page(params[:page]).per(50)
With paginated search results, the feature in features/searching.feature will no longer
complain when you run it with bin/cucumber features/searching.feature:
3 scenarios (3 passed)
39 steps (39 passed)