Rails%203%20In%20Action

Put this line:
Deleting a tag
And "user@ticketee.com" can tag the "Ticketee" project
With your all-powerful step defined in features/step_definitions/permission_steps.rb,
you don’t have to define a definition for this step to work. When you re-run this scenario
using bin/cucumber features/creating_comments.feature:48, it will pass:
1 scenario (1 passed)
16 steps (16 passed)
One scenario down, one to go! The next one is the features/creating_tickets.feature:51
scenario. At the top of the feature, you can put the same line you used in the “Creating
comments” feature, right under the view permission. Don’t forget to rename the
project:
And "user@ticketee.com" can tag the "Internet Explorer" project
This scenario too will pass:
1 scenario (1 passed)
16 steps (16 passed)
Great! Only certain users can now tag tickets. Let’s make sure that everything is still
running at 100% by running rake cucumber:ok spec. You should see this:
55 scenarios (55 passed)
608 steps (608 passed)
# and
38 examples, 0 failures, 18 pending
In this section, you have restricted the ability to add tags to a ticket—whether through
the new ticket or comment forms—to only users who have the permission to tag.
You’ve done this to restrict the flow of tags. Generally speaking, the people with the
ability to tag should know only to create useful tags, so that the usefulness of the tags is
not diluted. In the next section, you’ll use this same permission to determine what
users are able to remove a tag from a ticket.
11.4 Deleting a tag
Removing a tag from a ticket is a helpful feature, because a tag may become irrelevant
over time. Say that you’ve tagged a ticket as v0.1 for your project, but the feature isn’t
yet complete and needs to be moved to v0.2. Without this feature, there will be no way
to delete the old tag. Then what? Was this ticket for v0.1 or v0.2? Who knows? With the
ability to delete a tag, you have some assurance that people
will clean up tags if they’re able to.
To let users delete a tag, add an X to the left of each
of your tags, as shown in figure 11.4.
When this X is clicked, the tag will disappear through
the magic of JavaScript. Rather than making a whole
request out to the action for deleting a tag and then
redirecting back to the ticket page, remove the tag’s ele- Figure 11.4 X marks the spot
297