Rails%203%20In%20Action

Beginning the tickets API
Listing 13.22 spec/api/v1/projects_spec.rb
context "index" do
...
let(:url) { "/api/v1/projects/#{project.id}/tickets" }
it "XML" do
get "#{url}.xml", :token => token
last_response.body.should eql(project.tickets.to_xml)
end
it "JSON" do
get "#{url}.json", :token => token
last_response.body.should eql(project.tickets.to_json)
end
end
You’ve defined the let(:url) here to point to the nested route for tickets of a given
project. This URL is currently undefined and so when you run this test with bin/rspec
spec/api/v1/tickets_spec.rb, you’re told that the route you’re requesting doesn’t
exist:
Failure/Error: get "#{url}.json", :token => token
ActionController::RoutingError:
No route matches [GET] "/api/v1/projects/1/tickets.json"
You can define this route easily inside config/routes.rb by changing these lines
namespace :api do
namespace :v1 do
resources :projects
end
end
to this:
namespace :api do
namespace :v1 do
resources :projects do
resources :tickets
end
end
end
Now you’ve got the tickets resource nested within projects for your API again. When
you re-run this spec you’ll be told this:
uninitialized constant Api::V1::TicketsController
You can create this controller by creating a new file at app/controllers/api/v1/
tickets_controller.rb. This controller needs to first of all respond to both JSON and
XML, and find the project for each request using a before_filter. You can begin to
define this controller using the code from the following listing.
375