Rails%203%20In%20Action

esources :tickets do
resources :comments
resources :tags do
member do
delete :remove
end
end
end
Deleting a tag
By nesting the tags resource inside the ticket’s resource, you are given routing helpers
such as ticket_tag_path. With the member block inside the resources :tags, you can
define further actions that this nested resource responds to. You’ll define that you
should accept a DELETE request to a route to a remove action for this resource, which
you should now create.
Before you add this action to the TagsController, you must first generate this controller
by using
rails g controller tags
Now that you have a controller to define your action in, let’s open app/controllers/
tags_controller.rb and define the remove action in it like this:
def remove
@ticket = Ticket.find(params[:ticket_id])
if can?(:tag, @ticket.project) || current_user.admin?
@tag = Tag.find(params[:id])
@ticket.tags -= [@tag]
B Remove tag
@ticket.save
render :nothing => true
end
end
In this action, you find the ticket based on the id passed through as params[:ticket],
and then you do something new. On the left side of -= B you have @ticket.tags. On
the right, is an array containing @tag. This combination will remove the tag from the
ticket, but will not delete it from the database.
On the second-to-last line of this action, you save the ticket minus one tag. On the
final line you tell it to return nothing, which will return a 200 OK status to your
browser, signaling that everything went according to plan.
When you re-run your scenario it will now successfully click the link, but the tag is
still there:
When I follow "delete-this-tag-must-die"
Then I should not see "this-tag-must-die"
Failed assertion, no message given. (MiniTest::Assertion)
Your tag is unassociated from the ticket but not removed from the page, and so your
feature is still failing. The request is made to delete the ticket, but there’s no code currently
that removes the tag from the page. There are two problems you must overcome
to make this work. The first is that there’s no code. That part’s easy, and you’ll
301