You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 27, 2018. It is now read-only.
I like this, but as I mentioned on #13 I'm seeing Fluxo as just a "state manager", actions handlers and things like this "don't belong" to this package scope. Of course it's a ongoing discussion, here and on the other issue.
I see a better future creating a separate package for this action handler base (no problem if it'll be related to Fluxo), even if it's a small package.
Partially agree because it would increase the friction to start since we already need two packages.
We can make a meta package like rspec and rails does, fluxo would be a package which simply depends on fluxo-store, fluxo-react-connect-stores, fluxo-action.
I'm implementing action handlers as classes, example:
This is a superfluous example but the point is that the almost all methods are delegates to the store.
I'm thinking in having something like rails'
delegate
to reduce the boilerplate:You can see that delegates is generic and not related to the store itself, we could be delegating any method to any object.
What you think?
The text was updated successfully, but these errors were encountered: