Leave out store from the boilerplate

[timuric]

There are large variety of store implementations these days, and looks like Fynx is quite unpopular if not abandoned. Redux is getting a lot of attention atm and god knows what would be popular in next few weeks. Wouldn't be better to remove store from the Reapp() wrapper so that users could easier connect stores of their own choice?

[natew]

It's not a part of reapp-ui, just reapp-kit which is meant to give people a full-stack so they don't have to worry about anything.

Granted Redux seems popular, but it feels very heavy. But if someone PR'ed a change over to Redux I'd consider merging it if it seemed easier to use and better generally.

[timuric]

@natew I am currently using Reapp with Redux, and I am not sure how much you can stack Redux into a helper like Reapp() since you would need to define an extra mapToProps function, and define reducers somewhere. Also it is common when using Redux to add custom middleware for the store, such as loggers and various devtools.

I think that for users that want full stack setup it is easier to start from boilerplate projects like Reapp's Kitchen sink, which can come in various configurations. And probably users that start from CLI would expect a more flexible blank project. But that is just my opinion :)

[rhblind]

Hi,
I totally agree! I'm also using Redux with Reapp and have encountered issues passing dispatcher actions and state to the wrapped Reapp component.

+1

[natew]

Just use Redux and Reapp-ui, and take out the kit!

Really though this repo needs some love. I'm working on a new project that is really awesome though, perhaps once that comes out I can revisit this, are they are somewhat related. (Check my public activity for more info on it).

[timuric]

@natew is it about flintjs?

[natew]

Perhaps..