Rails%203%20In%20Action

306 CHAPTER 11 Tagging
The :from option tells Searcher what association this label should be searched upon,
and the :field option tells it what field to perform a lookup on.
The label method is evaluated internally to Searcher and will result in a by_tag
method being defined on your Ticket model, which will be used by the search
method if you pass in a query such as tag:iteration_1. This method will perform an
SQL join on your tags table, returning only the tickets that are related to a tag with the
given name.
With this configuration now in your model, you can define the search action
directly underneath the destroy action in TicketsController to use the search
method on Ticket:
def search
@tickets = @project.tickets.search(params[:search])
end
Assign all the tickets retrieved with the search method to the @tickets variable, which
you would render in the search template if you didn’t already have a template that was
useful for rendering lists of tickets. That template would be the one at app/views/
projects/show.html.erb, but to render it you’re going to make one small modification.
Currently this template renders all the tickets by using this line to start:
This line will iterate through the tickets in the project and do whatever is inside the
block for each of those tickets. If you were to render this template right now with the
search action, it would still return all tickets. You can get around this by changing the
line in the template to read
With this change, you break the ProjectsController’s show action, because the
@tickets variable is not defined there. You can see the error you would get when you
run bin/cucumber features/viewing_tickets.feature:
You have a nil object when you didn't expect it!
You might have expected an instance of Array.
The error occurred while evaluating nil.each
To fix this error, you set up the @tickets variable inside the show action of Projects-
Controller, which you should place directly under the definition for the index
action:
def show
@tickets = @project.tickets
end
When you re-run bin/cucumber features/viewing_tickets.feature, you see that it
now passes once again:
1 scenario (1 passed)
23 steps (23 passed)