Terry Appleby

I think its nice to be able to specify the actionId but I almost wonder if its possible to just have `Flux#createAction(actionCreator)` as well.

I was picturing the `createAction` to be similar to what the `Actions#_wrapAction` method is currently doing where you dont really need the raw (string) action id. something like: ``` js...

That could work. only part Im not so sure about is when triggering an action from a component, currently I use something like: ``` let sessionActions = this.flux.getActions('core.session'); sessionActions.login(email, pass);...

With my stores I usually pass in the actions directly instead of the flux instance, simplifies testing a bit: ``` js let sessionActions = keyMirror({login: null, logout: null, receiveSession: null});...

Yeah I'm running into the same issues, still haven't come up with a good solution yet. Things are not so bad in simple apps but as soon as you have...

Yeah I wonder if its a query language or perhaps a base set of stores for avoiding all the boilerplate (similar to @gaearon has).

yeah make is nice, doesn't work well for windows users though.

Laravel 4.3 support will show up a bit closer to its release date, 4.3 is still in development and things are subject to change. The interface changes cause some issues...

Interesting idea, though Im not sure what the security implications would be of using the session like this. The sessions ID's might not be generated with enough entropy or authentication...

haven't tried them out yet but Dingo and Fractal look very handy. You are correct about JWT, it is just signing the data so you need to be careful about...