We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Upgrading from 1.10 to 1.11-beta-4 I ran into the following issue.
In the router when rendering templates in the renderTemplate hook the into property used to default to the parent template.
renderTemplate
into
The following used to work.
/routes/timecards/day.js export default Ember.Route.extend( renderTemplate: function() { this.render('timecards/day/title', { outlet: 'timecardsTitle', }); this.render('timecards/user/days'); },
It now throws an exception
Error while processing route: timecards.day Assertion Failed: An outlet (timecardsTitle) was specified but was not found.
The error goes away if if add an into property to any render calls with an outlet property.
outlet
So it seems the render function doesn't have a default into property when the outlet property is specified.
The text was updated successfully, but these errors were encountered:
Some JSBins illustrating the issue:
1.11.0-beta.1 works: http://emberjs.jsbin.com/viyodiqobi/5/edit 1.11.0-beta.2 onwards doesn't work http://emberjs.jsbin.com/wejekavuba/2/edit
Related to #10478?
Sorry, something went wrong.
I was able to solve this issue by adding the name of the template where the outlet is located.
App.PostsShowRoute = Ember.Route.extend({ renderTemplate: function() { this.render({ outlet: "body", into: "posts" }); } });
Successfully merging a pull request may close this issue.
Upgrading from 1.10 to 1.11-beta-4 I ran into the following issue.
In the router when rendering templates in the
renderTemplate
hook theinto
property used to default to the parent template.The following used to work.
It now throws an exception
The error goes away if if add an
into
property to any render calls with anoutlet
property.So it seems the render function doesn't have a default
into
property when theoutlet
property is specified.The text was updated successfully, but these errors were encountered: