Rails%203%20In%20Action

into these:
resources :projects do
resources :tickets do
collection do
get :search
end
end
end
Finding tags
The collection block here defines that there’s a search action that may act on a collection
of tickets. This search action will receive the parameters passed through from
the form_tag you have set up. When you run your feature again by using bin/cucumber
features/searching.feature, you see that it’s reporting that the search action is
missing:
And I press "Search"
The action 'search' could not be found for TicketsController
Good! The job of this action is to find all the tickets that match the criteria passed in
from the form as params[:search], which is what you can use the Searcher gem for.
11.5.2 Searching by state with Searcher
The Searcher gem provides the functionality of parsing the labels in a query such as
tag:iteration_1 and determines how to go about finding the records that match the
query. Rather than working like Google, where you could put in iteration_1 and it
would know, you have to tell it what iteration_1 means by prefixing it with tag:. You
use this query with the search method provided by Searcher on a configured model,
and it will return only the records that match it:
Ticket.search("tag:iteration_1")
You’ll use this method in the search action for TicketsController in a bit.
The first port of call to begin to use the Searcher gem is to add it to your Gemfile
underneath gem 'paperclip':
gem 'searcher'
To install this gem, you run bundle install. Now for the configuration. Searcher is
configured by a searcher call in a class, just as associations are set up by using
has_many and friends. In app/models/ticket.rb directly above 5 the first belongs_to,
put this code:
searcher do
label :tag, :from => :tags, :field => :name
end
5 Code from gems or plugins should go above any code for your models, because it may modify the behavior
of the code that follows it.
305