Don't advertize deprecated initializer functionality

[zeppelin]

Since the Ember container/registry separation, calling lookup in initializers is deprecated and available only for backwards-compatibility, yet it's usage is still advertised in the ApplicationRouteMixin's documentation. It would be good if an alternative solutuion was offered instead.

[vire]

@zeppelin could you submit a PR with an alternative solution? I'm very interested in this concept because I've used a lot of container.lookup in initializers.

Thanks!

[zeppelin]

@vire absolutely, but it'd be even better if we could get expert advice from @dgeb, he did the container/registry refactor.

[marcoow]

It would probably be god to use Ember's new service injection API.

@dgeb: would that be the suggested way of making the session available, e.g.

//app/components/my-component.js
export default Ember.Component.extend({
  session: authManager: Ember.inject.service('session')
})

?

[dgeb]

If you want to make a service available on a particular component, then you can definitely use the service injection API.

Note that:

//app/components/my-component.js
export default Ember.Component.extend({
  session: Ember.inject.service('session')
});

Is equivalent to:

//app/components/my-component.js
export default Ember.Component.extend({
  session: Ember.inject.service()
});

This is because the property is named the same as the service (session).

You can certainly also call application.inject() from an initializer to make a service available more broadly (say, to all routes).

I've opened an RFC to steer the registry / container / initializer work in the direction I'd like to take it: emberjs/rfcs#46

[marcoow]

Thanks @dgeb! Ember Simple Auth now uses the application's register and inject methods rather than the container's register and injection.

[dgeb]

Great - glad to help!