Managing dependencies between controllers
Often, controllers will need to access other controllers' properties and models. This is especially important when you have nested resources. In this recipe, we'll take a look at a nested controller that needs access to the parent controller's model and properties.
How to do it...
- In a new application, generate a couple of new routes and templates:
$ ember g route foo1 $ ember g route foo1/foo2 $ ember g controller foo1 $ ember g controller foo1/foo2 $ ember g template index
This generates the
foo2routes and controllers. The
foo2route is a nested route. The index template will contain links.
- Verify in the
router.jsfile that all the routes have been created correctly:
// app/router.js import Ember ...