One of the most important jobs of a route handler is rendering the appropriate template to the screen.
By default, a route handler will render the template into the closest parent with a template.
Router.map(function() {
this.route('posts');
});
export default Ember.Route.extend();
If you want to render a template other than the one associated with the
route handler, implement the renderTemplate
hook:
export default Ember.Route.extend({
renderTemplate: function() {
this.render('favoritePost');
}
});
If you want to use a different controller than the route handler's
controller, pass the controller's name in the controller
option:
export default Ember.Route.extend({
renderTemplate: function() {
this.render({ controller: 'favoritePost' });
}
});
Ember allows you to name your outlets. For instance, this code allows you to specify two outlets with distinct names:
So, if you want to render your posts into the sidebar
outlet, use code
like this:
export default Ember.Route.extend({
renderTemplate: function() {
this.render({ outlet: 'sidebar' });
}
});
All of the options described above can be used together in whatever combination you'd like:
export default Ember.Route.extend({
renderTemplate: function() {
var controller = this.controllerFor('favoritePost');
// Render the `favoritePost` template into
// the outlet `posts`, and use the `favoritePost`
// controller.
this.render('favoritePost', {
outlet: 'posts',
controller: controller
});
}
});
If you want to render two different templates into outlets of two different rendered templates of a route:
export default Ember.Route.extend({
renderTemplate: function() {
this.render('favoritePost', { // the template to render
into: 'posts', // the template to render into
outlet: 'posts', // the name of the outlet in that template
controller: 'blogPost' // the controller to use for the template
});
this.render('comments', {
into: 'favoritePost',
outlet: 'comment',
controller: 'blogPost'
});
}
});