New stateFor CP

[thoov]

Solves: #28

This gives the following syntax:

import Ember from 'ember';
import stateFor from 'ember-state-services/stateFor';

export default Ember.Component.extend({
  data: stateFor('state-name', { key: 'state-key' })
});

@stefanpenner I need to talk with you about how we should handle "default" state. Before this was done inside of the users own service file (inside setupState override) but now this is done behind the scenes.

[stefanpenner]

@stefanpenner I need to talk with you about how we should handle "default" state. Before this was done inside of the users own service file (inside setupState override) but now this is done behind the scenes.

i wonder if we should allow for a callback to be provided straight to this CP to be a "factory" or builder

if we need to reuse it maybe it should be a static method on the state object.

var MyState = Ember.Object.extend(...);

MyState.reopenClass({
  setupState(key, container) {
    return this.create(...)
  }
})

or is es6

class MyState extends Ember.Object {
  static setupState(...)  {...}
}

[thoov]

@stefanpenner Ok take a look now. I added this:

BufferedProxy.reopenClass({
  initialState() {
    return { content: this.get('email') };
  }
});

[stefanpenner]

LGTM

[thoov]

I'm going to merge this so I can use it with my new example PR that I will be sending later today

[stefanpenner]

@thoov hey, got time to update the readme?

[thoov]

Yes I will update it with my next PR

[stefanpenner]

@thoov awesome thanks!