Rails%203%20In%20Action

Mounting a Rack application with Rails
This is because you haven’t yet defined the module for the Api::V3 namespace. Let’s
create a new file at app/controllers/api/v3/json/tickets.rb that defines this module, as
shown in the following listing.
Listing 18.8 app/controllers/api/v3/json/tickets.rb
require 'sinatra'
module Api
module V3
module JSON
class Tickets < Sinatra::Base
before do
headers "Content-Type" => "text/json"
end
get '/' do
[]
end
end
end
end
end
Within this file you define the Api::V3::JSON::Tickets class that is described at the
top of your spec, which will now make your spec run. This class inherits from Sinatra::Base
so that you’ll get the helpful methods that Sinatra provides, such as the
before B and get methods that you use here. You’ve already seen what get can do,
but before is new. This method is similar to a before_filter in Rails and will execute
the block before each request. In this block, you set the headers for the request, using
Sinatra’s headers method, so that your API identifies as sending back a text/json
response.
Let’s rerun it using bin/rspec spec/api/v3/json/tickets_spec.rb:
Failure/Error: get url, :token => token
ActionController::RoutingError:
No route matches [GET] "/api/v3/json/projects/1/tickets"
This is a better start: now your test is running and failing as it should because you
haven’t defined the route for it yet. Your test is expecting to be able to do a GET
request to /api/v3/json/projects/1/tickets but cannot.
This route can be interpreted as /api/v3/json/projects/:project_id/tickets, and you
can use the api namespace already in config/routes.rb to act as a home for this route.
Let’s put some code for v3 of your API inside this namespace now:
namespace :v3 do
namespace :json do
mount Api::V3::JSON::Tickets,
:at => "/projects/:project_id/tickets"
end
end
B Before method
529