Rails%203%20In%20Action

114 CHAPTER 5 Nested resources
Again, you’re defining the action here so that anybody coming through and reading
your TicketsController class knows that this controller responds to this action. It’s
the first place people will go to determine what the controller does, because it is the
controller.
The next logical step is to create the view for this action. Put it at app/views/
tickets/edit.html.erb and fill it with this content:
Editing a ticket in
Here you re-use the form partial you created for the new action, which is handy. The
form_for knows which action to go to. If you run the feature command here, you’re
told the update action is missing:
And I press "Update"
The action 'update' could not be found TicketsController
5.3.2 Adding the update action
You should now define the update action in your TicketsController, as shown in the
following listing.
Listing 5.14 app/controllers/tickets_controller.rb
def update
if @ticket.update_attributes(params[:ticket])
flash[:notice] = "Ticket has been updated."
redirect_to [@project, @ticket]
else
flash[:alert] = "Ticket has not been updated."
render :action => "edit"
end
end
Remember that in this action you don’t have to find the @ticket or @project objects
because a before_filter does it for the show, edit, update, and destroy actions. With
this single action implemented, both scenarios in your ticket-editing feature pass:
2 scenarios (2 passed)
20 steps (20 passed)
Now check to see if everything works:
12 scenarios (12 passed)
100 steps (100 passed)
# and
5 examples, 0 failures, 4 pending
Great! Let’s commit and push that:
git add .
git commit -m "Implemented edit action for the tickets controller"
git push