This is nice but I can imagine it would still require a lot of boilerplate code in order to integrate nicely into a flux architecture in a production app. Comparatively, I think Fluxible does a good job in separating the async logic while providing you with clean Flux terms. Would be interested to see some higher-level integration library with Redux, Alt or a flux library.
It's not much more than an additional 1 or 2 decorators, & even those can be a local file specific to how you write your app. In my experience, I only add a `@dispatcher()` decorator above it, and use `@resolve` as normal. 1 line doesn't constitute "a lot of boilerplate" in my opinion :)
I intentionally didn't couple this with a specific Flux lib since _this solves an entirely different problem_ than maintaining application state.
Look forward the Redux & Alt example, though, as those will have a very terse, so you won't have to use your imagination anymore!
Comments
This is nice but I can imagine it would still require a lot of boilerplate code in order to integrate nicely into a flux architecture in a production app. Comparatively, I think Fluxible does a good job in separating the async logic while providing you with clean Flux terms. Would be interested to see some higher-level integration library with Redux, Alt or a flux library.
It's not much more than an additional 1 or 2 decorators, & even those can be a local file specific to how you write your app. In my experience, I only add a `@dispatcher()` decorator above it, and use `@resolve` as normal. 1 line doesn't constitute "a lot of boilerplate" in my opinion :)
I intentionally didn't couple this with a specific Flux lib since _this solves an entirely different problem_ than maintaining application state.
Look forward the Redux & Alt example, though, as those will have a very terse, so you won't have to use your imagination anymore!