Rails%203%20In%20Action

Creating tickets
ticket URL is always scoped by /projects/:id in your application. This helper and its
brethren are defined by changing this line in config/routes.rb
resources :projects
to the lines in the following listing.
Listing 5.3 config/routes.rb
resources :projects do
resources :tickets
end
This code tells the routing for Rails that you have a tickets resource nested inside the
projects resource. Effectively, any time you access a ticket resource, you access it within
the scope of a project too. Just as the resources :projects method gave you helpers to
use in controllers and views, this nested one gives you the helpers (where id represents
the identifier of a resource) shown in table 5.1.
Table 5.1 Nested RESTful routing matchup
As before, you can use the *_url alternatives to these helpers, such as project
_tickets_url, to get the full URL if you so desire. The :project_id symbol here
would normally be replaced by the project ID as well as the :id symbol, which would
be replaced by a ticket’s ID.
In the left column are the routes that can be accessed, and in the right, the routing
helper methods you can use to access them. Let’s make use of them by first creating
your TicketsController.
5.1.2 Creating a tickets controller
Route Helper
/projects/:project_id/tickets project_tickets_path
/projects/:project_id/tickets/new new_project_ticket_path
/projects/:project_id/tickets/:id/edit edit_project_ticket_path
/projects/:project_id/tickets/:id project_ticket_path
Because you defined this route in your routes file, Capybara can now click the link in
your feature and proceed before complaining about the missing TicketsController,
spitting out an error followed by a stack trace:
And I follow "New Ticket"
uninitialized constant TicketsController ...
Some guides may have you generate the model before you generate the controller,
but the order in which you create them is not important. In Cucumber, you just
follow the bouncing ball, and if Cucumber tells you it can’t find a controller, then
you generate the controller it’s looking for next. Later, when you inevitably receive
101