Rails%203%20In%20Action

Deleting projects
default, this prompt is ignored, so you don’t have to tell Capybara to click OK on the
prompt—there is no prompt because Rails has a built-in fallback for users without
JavaScript enabled. If you launch a browser and follow the steps in the feature to get
to this Delete Project link, and then click the link, you see the confirmation prompt.
This prompt is exceptionally helpful for preventing accidental deletions.
When you run the feature again, it complains of a missing destroy action:
And I follow "Delete Project"
The action 'destroy' could not be found for ProjectsController
The final action you need to implement is in your controller, and you’ll put it underneath
the update action. This action is shown in the following listing.
Listing 4.15 app/controllers/projects_controller.rb
def destroy
@project = Project.find(params[:id])
@project.destroy
flash[:notice] = "Project has been deleted."
redirect_to projects_path
end
Here you call the destroy method on the @project object you get back from your
find. No validations are run here, so no conditional setup is needed. Once you call
destroy on that object, the relevant database record is gone for good but the object
still exists. When it’s gone, you set the flash[:notice] and redirect back to the project’s
index page by using the projects_path routing helper.
With this last action in place, your newest feature should pass when you run bin/
cucumber features/deleting_projects.feature:
1 scenario (1 passed)
6 steps (6 passed)
Let’s see if everything else is running with rake cucumber:ok:
6 scenarios (6 passed)
37 steps (37 passed)
Great! Let’s commit that:
git add .
git commit -m "Implemented delete functionality for projects"
git push
Done! Now you have the full support for CRUD operations in your Projects-
Controller. Let’s refine this controller into simpler code before we move on.
4.3.3 Looking for what isn’t there
People sometimes poke around an application looking for things that are no longer
there, or they muck about with the URL. As an example, launch your application’s
server by using rails server and try to navigate to http://localhost:3000/projects/
not-here. You’ll see the exception shown in figure 4.1.
93