Support for sub state managers on router

[tchak]

What I am doing right now is this :

Ember.onLoad('application', function(app) {
  app.registerInjection({
    name: 'stateManagers',
    after: 'controllers',
    injection:  function(app, router, property) {
      if (!/^[A-Z].*StateManager$/.test(property)) { return; }

      var name = property[0].toLowerCase() + property.substr(1),
          stateManager = app[property].create();

      stateManager.set('router', router);
      router.set(name, stateManager);
      Ember.keys(router).forEach(function(key) {
        if (/^[a-z].*Controller$/.test(key)) {
          stateManager.set(key, router.get(key));
        }
      });
    }
  })
});

And I modified transitionTo to accept as first argument the name of state manager you want to run transition on.
I am planing to do more work to make the experience as transparent as possible

Would there be interest in adopting something like this in core?

[ghempton]

I think we need a more generic injection mechanism that would support injecting anything (e.g. currentUser, state managers, etc.). Seems like we also need a way to signal classes that shouldn't be injected.

[wagenet]

@tchak What's the current thought on this?

[tchak]

I am currently using a sort of "triage" in the send on the router. It can rerout some events on sub event managers.
I can write a proposal for this, if there enough interest.

[wagenet]

@tchak I feel like it's something that definitely would be useful, though we'd want to think carefully about how to do it without confusing users.

[wagenet]

@tchak How does this play in with the new router?

[wagenet]

This isn't directly applicable to the new router.