API idea.

[stefanpenner]

rather then inject + cp

it would be nice to do.

state: stateFor('email', { key: 'email' })

// or

state: stateFor('email', { key: function(attr, state) { return // w/e you can think of})

in most cases we can likely auto-generate the state service itself, only making the state objects something the user needs to deal with.

cc @thoov

[thoov]

@stefanpenner I agree with auto-generating the state service or at least doing something behind the scenes so that it is hidden from the users point of view.

How would the user get stateFor in your example if they are not going to inject it?

[stefanpenner]

How would the user get stateFor in your example if they are not going to inject it?

import

[thoov]

If you simply import stateFor how would it get access to the container?

I assume you are talking about something like this:

// state-for.js
export default function(stateName, options) {
  // get state from container

  // or simply keep a 'dumb' hashMap here and just reference it instead???

  return state
};

// my-cool-component.js
import Ember from 'ember';
import stateFor from 'path/to/state-for';

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

[stefanpenner]

@thoov the same way CP's work. (it would just be a type of CP)

[thoov]

Ok let me whip something up

[stefanpenner]

👍

[jasonmit]

Nice work @thoov. Docs need to be updated to reflect the PR 👍

[thoov]

@jasonmit ya I am sending another PR with an updated example and I will be updating the readme