Follow up on: emberjs/ember.js#18452
Basically, as of now, if you are using pods layout and have a route like this:
app/my-route/template.hbs
It will always take this template when invoking a <MyRoute /> component, even if there is a more "specific" component defined somewhere (e.g. app/components/my-route/template.hbs).
As suggested by @rwjblue , it would be great if you could somehow deactivate this behavior. Either just for the new co-located components, or also for the above pods syntax. As it basically means that you cannot have a component with the same name as any route.
Follow up on: emberjs/ember.js#18452
Basically, as of now, if you are using pods layout and have a route like this:
app/my-route/template.hbsIt will always take this template when invoking a
<MyRoute />component, even if there is a more "specific" component defined somewhere (e.g.app/components/my-route/template.hbs).As suggested by @rwjblue , it would be great if you could somehow deactivate this behavior. Either just for the new co-located components, or also for the above pods syntax. As it basically means that you cannot have a component with the same name as any route.