Rails%203%20In%20Action

300 CHAPTER 11 Tagging
true,
:url => remove_ticket_tag_path(@ticket, tag),
:method => :delete,
:html => { :id => "delete-#{tag.name.parameterize}" } %>
Here, you check that a user can tag in the ticket’s project. If they can’t tag, then you
won’t show the X to remove the tag. This is to prevent everyone from removing tags as
they feel like it. Remember? With great power comes great responsibility.
You use the :remote option for the link_to, to indicate to Rails that you want this
link to be an asynchronous request. This is similar to the Add Another File button you
provided in chapter 9, except this time you don’t need to call out to any JavaScript to
determine anything, you only need to make a request to a specific URL.
For the :url option here, you pass through the @ticket object to remove_ticket
_tag_path so that your action knows what ticket to delete the tag from. Remember:
your primary concern right now is disassociating a tag and a ticket, not completely
deleting the tag.
Because this is a destructive action, you use the :delete method. You’ve used this
previously for calling destroy actions, but the :delete method is not exclusive to the
destroy action, and so you can use it here as well.
The final option, :html, lets you define HTML attributes for the link. Inside this
hash, you set the id key to be the word delete, followed by a hyphen and then the name
of your tag parameterize’d. For the tag in your scenario, this is the id that you’ll use
to click this link. Capybara supports following links by their internal text, the name
attribute, or the id attribute.
When you run your feature with bundle exec cucumber features/deleting_tags
.feature, you see that it reports the same error message at the bottom:
When I follow "delete-this-tag-must-die"
no link with title, id or text 'delete-this-tag-must-die'
Ah! A quick eye would have spotted an error when the browser launched by Web-
Driver tried going to this page; it looks like figure 11.5.
This error is coming up because you haven’t defined the route to the remove
action yet. You can define this route in config/routes.rb inside the resources :tickets
block, morphing it into this:
Figure 11.5 Internal Server Error