Rails%203%20In%20Action

Creating tags
side of the association. A join table’s sole purpose is to
join together the two tables whose keys it has. In this
case, the two tables are the tickets and tags tables. As
you move forward in developing this association, note
that, for all intents and purposes, has_and_belongs_to
_many works like a two-way has_many.
Figure 11.1 The tag box
You’ll create two ways to add tags to a ticket. A text
field for new tickets beneath the ticket’s description field will allow users to add multiple
tags by using a space to separate different tags, as shown in figure 11.1.
Additional tags may also be added on a comment, with a text field similar to the
one from the new ticket page providing the tagging mechanism. When a ticket is created,
you’ll show these tags underneath the description, as shown in figure 11.2.
When a user clicks a tag, they’ll be taken to a page where they can see all tickets
with that particular tag. Alternatively, if the user clicks the little “x” next to the tag,
that tag will be removed from the ticket. The actions of adding and removing a tag are
both actions you’ll add to your permission checking.
Finally, you’ll implement a way to search for tickets
that match a state, a tag, or both, by using a gem called
searcher. The query will look like tag:iteration_1
state: open.
That’s all there is to this chapter! You’ll be adding
tags to Ticketee, which will allow you to easily group and
sort tickets. Let’s dig into your first feature, adding tags Figure 11.2 A tag for a ticket
to a new ticket.
11.1 Creating tags
Tags in this application will be extremely useful for making similar tickets easy to find
and manage. In this section, you’ll create the interface for adding tags to a new ticket
by adding a new field to the new ticket page and defining a has_and_belongs
_to_many association between the Ticket model and the not-yet-existent Tag model.
11.1.1 Creating tags feature
You’re going to add a text field beneath the description field on the new ticket page
for this feature, as you saw earlier in figure 11.1.
The words you enter into this field will become the tags for this ticket, and you
should see them on the ticket page. At the bottom of features/creating_tickets.feature,
you add a scenario that creates a new ticket with tags, as shown in listing 11.1.
Listing 11.1 features/creating_tickets.feature
Scenario: Creating a ticket with tags
When I fill in "Title" with "Non-standards compliance"
And I fill in "Description" with "My pages are ugly!"
And I fill in "Tags" with "browser visual"
287