Forgive my slowness but I’m still struggling to understand what you’re going for. Perhaps you could create a jsbin that produces the output you desire with a view and then I can help you make it not a view. http://emberjs.jsbin.com/
I think the real problem is that we are supposed to remove all Ember.Views, but we cannot replace them with Components because there are no Routable Components yet. Would be very cool if we could get some official guidance what to do in such scenarios…
I started ember as views were being phased out so I’m not too familiar with the range of problems they solve that can’t be solved by components / controllers in the current setup. Perhaps if you post them, I or others in the community, can try and help.
Not doing anything else there. I just enjoy having a clean DOM. I know it is not the most important thing in the world.
Simply changing it to Component.extend works well to get rid of the deprecation!
The File in my ES6 modules is still called application/view.js though. (I’m using POD structure). I know I’m being a little too pedantic here.
Unless you are trying to avoid touching your index.html or have another use for view/application.js; this should be better and you are saving yourself an extra Ember.Component / Ember.View layer that you need to go through.
Nevermind, I just realized this doesn’t solve your problem. You do want to override the ApplicationView, which is deprecated… I have no idea how to solve this and I do remember trying.
Edit: Talked to runspired in Slack. Basically, stick with Ember.View() until the Route Components are added into core
Currently we are at Ember 2.2, which has neither views nor routable components. Is there a solution for this? I’m trying to set a class on the outermost ember-view div and don’t want to inadvertently select other sibling divs.
Thanks. I was aware of ember-legacy-views. Kind of a big hammer for a small nail, though.
I was more thinking of a way within ember core to achieve this. I assume once the application template becomes a component, this can easily done by setting the classNames on that component. In the interim, I haven’t found a better way than using a little jQuery at runtime.