Rails%203%20In%20Action

372 CHAPTER 13 Designing an API
@project.reload
@project.name.should eql("Ticketee")
errors = { :name => ["can't be blank"]}
last_response.body.should eql(errors.to_json)
end
In this example, you attempt to set the project’s name to a blank string, which should
result in the 422 error you want to see. After you reload the project, the name should
be the same. You should then get the 422 error as the response.
A quick run of bin/rspec spec/api/v1/projects_spec.rb should let you know if
this is working:
7 examples, 0 failures
Indeed it is! Is everything else working? A run of rake spec will let you know:
51 examples, 0 failures, 19 pending
“51 examples, 0 failures” is exactly what you like to see. That means that your update
action is all wrapped up, and now it’s time for a commit:
git add .
git commit -m "Implement update action for projects API"
git push
You’ve now got three fourths of the CRUD of this API. You’re able to create, read, and
update project resources. With updating, clients authorized with an admin’s token
can send through updates to the project resource, which will update the information
in the application. The one remaining action you’ve got to implement is the destroy
action, for making projects go bye-bye. You’re almost home!
13.1.11 Exterminate!
You need to create the destroy action, which allows admins of Ticketee to delete projects
through the API. To do this, API clients need to make a DELETE request to /api/
v1/projects/1.json or /api/v1/projects/1.xml. Upon making this request, the specified
project will be deleted—gone forever, exterminated!
You’ll write the final example in the spec/v1/api/projects_spec.rb to make sure
that people are able to delete projects using this route. You’ll use the code from the
following listing to do this.
Listing 13.20 spec/v1/api/projects_spec.rb
context "deleting a project" do
before do
user.admin = true
user.save
end
let(:url) { "/api/v1/projects/#{@project.id}" }
it "JSON" do
delete "#{url}.json", :token => token