Use Ember.get() to access store

[mike-north]

I'm playing with a few interesting use cases, which involve using the "route.js" mixin on objects other than a route (i.e., an Ember.Service or something).

Allowing the store to be accessed is not a big problem -- I can just add a CP on this object

  store: computed({
    get() {
      return this.container.lookup('store:main');
    }
  }),

Unfortunately, accessing this CP directly via a this.store, before the CP's getter function has been invoked for the first time, will end up returning the computed property its self, rather than the property's value.

This small change should maintain the existing use cases just fine, and also allow for potential usage that deviates from the well-traveled path.

[hhff]

Looks good mike! If you can green it off I'm happy to merge! I've also been scheming on the concept of of allowing the developer to describe a "promise generator" rather than relying on the ember data store, for folks who aren't using it.

Glad u found this use case before I started on that work...!

[mike-north]

@hhff ping

[kellyselden]

@mike-north

  store: computed({
    get() {
      return this.container.lookup('store:main');
    }
  }),

couldn't this work?

  store: Ember.inject.service(),

[hhff]

👍 Pretty sure inject doesn't work with the store @kellyselden

[hhff]

released 0.0.13