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
I discovered this strange behaviour that worked previously:
My router looks like this:
Router.map(function() { this.resource('application', {path: '/'}, function (){ }); });
My application.hbs
application.hbs
<h2 id="title">Welcome to Ember.js</h2> {{outlet}}
The rendered html:
<div id="ember336" class="ember-view"> <h2 id="title">Welcome to Ember.js</h2> <h2 id="title">Welcome to Ember.js</h2> <!----> </div>
I get the feeling that the application resource is always implicit and is not overriden if defined in the router.
application
jsbin: http://emberjs.jsbin.com/loricutuxa/1/edit
This is working (no double rendering) with 1.11.0-beta.1
1.11.0-beta.1
The text was updated successfully, but these errors were encountered:
LOL, double the outlet fun! I think we should make top level application name reserved, similar to basic and array.
basic
array
Sorry, something went wrong.
I agree, this was fixed by simply removing the application resource defined in the router. +1 for the fast reactions by the way.
Successfully merging a pull request may close this issue.
I discovered this strange behaviour that worked previously:
My router looks like this:
My
application.hbs
The rendered html:
I get the feeling that the
application
resource is always implicit and is not overriden if defined in the router.jsbin: http://emberjs.jsbin.com/loricutuxa/1/edit
This is working (no double rendering) with
1.11.0-beta.1
The text was updated successfully, but these errors were encountered: