connectOutlets from root state called before initialization?

Question

In root's connectOutlets, the App still seems un.initialize()d. Is connectOutlets not intended to be used with the root state? (And why?)

If I need something every time the page is loaded (such as in pangratz's NavigationView here: https://stackoverflow.com/a/11629977/363073), then I will need to have an all-inclusive root.index state like he does?

I think this discussion https://github.com/emberjs/ember.js/pull/941 will be usefull :) — sly7_7, Aug 01 '12 at 22:14
@sly7_7 Thank you! Going to use `{{view App.NavigationView controllerBinding="App.router.navigationController"}}` instead of `{{outlet "navigation"}}` based on trek's alternative from that discussion: https://github.com/emberjs/ember.js/pull/941#issuecomment-6848712 — dechov, Aug 01 '12 at 22:28
cool :), I think this is an answer to http://stackoverflow.com/questions/11767161/emberjs-router-pangratz-example-class-active — sly7_7, Aug 01 '12 at 22:35

score 0 · Accepted Answer · answered Aug 02 '12 at 16:09

As pointed out by sly7_7, this is still an open question -- apparently the functionality is considered desirable but seems to require an undesirable hack. http://github.com/emberjs/ember.js/pull/941

For now, either have all your routes in a subroute such as root.index, or manually bind the controller rather than using the outlet helper (e.g. {{view App.NavigationView controllerBinding="App.router.navigationController"}}).

connectOutlets from root state called before initialization?

1 Answers1

Linked