Rails%203%20In%20Action

310 CHAPTER 11 Tagging
into this:
"tag:#{tag.name}") %>
For this link_to, you use the search_project_tickets_path helper to generate a
route to the search action in TicketsController for the current ticket’s project, but
then you do something different. After you specify @ticket.project, you specify
options.
These options are passed in as additional parameters to the route. Your search
form passes through the params[:search] field, and your link_to does the same
thing. So you see that when you run bin/cucumber features/searching.feature
:35, this new scenario will now pass:
1 scenario (1 passed)
13 steps (13 passed)
This feature allows users to click a tag on a ticket’s page to then see all tickets that have
that tag. Let’s make sure you didn’t break anything with this small change by running
rake cucumber:ok spec. You should see this output:
59 scenarios (59 passed)
658 steps (658 passed)
# and
39 examples, 0 failures, 19 pending
Great, nothing broke! Let’s commit this change:
git add .
git commit -m "Users can now click a tag's name to go to
a page showing all tickets for it"
git push
Users are now able to search for tickets based on their state or tag, as well as go to a list
of all tickets for a given tag by clicking the tag name that appears on the ticket’s page.
This is the final feature you needed to implement before you have a good tagging system
for your application.
11.6 Summary
In this chapter, we’ve covered how to use a has_and_belongs_to_many association to
define a link between tickets and tags. Tickets are able to have more than one tag, but
a tag is also able to have more than one ticket assigned to it, and therefore you use this
type of association. A has_and_belongs_to_many could also be used to associate people
and the locations they’ve been to. 6
You first wrote the functionality for tagging a ticket when it was created, and then
continued by letting users tag a ticket through the comment form as well.
6 Like foursquare does.