Rails%203%20In%20Action

The projects API
last_response.status.should eql(200)
end
end
When you run bin/rspec spec/v1/api/projects_spec.rb, this spec will fail because
the destroy action doesn’t exist:
1) /api/v1/projects deleting a project JSON
Failure/Error: delete "#{url}.json", :token => token
The action 'destroy' could not be found for Api::V1::ProjectsController
You need to add the destroy action to the Api::V1::ProjectsController, which you
can do with this code:
def destroy
@project.destroy
respond_with(@project)
end
The respond_with here will respond with a 200 status code and an empty JSON or
XML response, which indicates the object was successfully destroyed. But where does
@project come from? Your before_filter should set this up, but it doesn’t right now.
Let’s fix it by changing it from this
before_filter :find_project, :only => [:show,
:update]
to this:
before_filter :find_project, :only => [:show,
:update,
:destroy]
When you run bin/rspec spec/api/v1/projects_spec.rb, does it pass?
8 examples, 0 failures
It does, because you’re great at what you do! That’s the final piece of the projects API,
and now people are able to create, read, update, and delete projects through it. The
rest of your specs probably pass because you didn’t change anything outside the
scope, but it’s still good to do a check. For old time’s sake, you’ll also run the features
to make sure everything’s ok there too. The full command that you’ll now run is rake
cucumber:ok spec. For this command, you should see this output:
63 scenarios (63 passed)
732 steps (732 passed)
# and
52 examples, 0 failures, 19 pending
All systems are go, so let’s make a commit at this lovely point in time where everything
is beautiful:
git add .
git commit -m "Projects can now be deleted through the API"
373