Port to Redux

[gaearon]

I intend to port this example to Redux.

I'm not doing that to promote my library, but because reusable store utilities (like pagination) are way easier to implement as pure functions. What I have right now in PaginatedStoreUtils is a mess, and will be much more sensible with Redux approach.

However, I understand that not everybody will be happy with this change, as Redux is not exactly Flux. I think it solves the same problems better than Flux, but that's my opinion and some may not share it.

Therefore I ask what you think:

• Should I rename the repository to reflect that it's a Redux example now?
• Should I keep the old vanilla Flux code in a branch?

To clarify again:

• I intend to keep it minimal, just like the current repo, and handle the same cases: pagination, “load more”, spinners.
• The “content stores” / “list stores” distinction will be even clearer with reusable reducers.
• This is not an artificial effort to port for the sake of porting. The code will be clearer after porting to Redux, and the idioms currently used by the code will be more apparent and natural.

Thoughts?

[felipeleusin]

Imho rename and kee pthe flux in an old branch and keep a link in the readme.... Between redux and react-router 1.0 there is going to be A LOT of changes. Also, thanks for all the work you've been doing with redux lately!

[ghost]

like @felipeleusin has said it, rename it and keep the old version. maybe as branch or maybe even only as link to current revision.

[davidwatkins73]

agree with @felipeleusin. V. interested in seeing this port.

[i4got10]

It might be better to make a new repository redux-react-router-example

[idolize]

Awesome, can't wait for this!

[gaearon]

The port will be part of the official Redux repo.
PR: reduxjs/redux#460

[gaearon]

The Redux port is here: https://github.com/rackt/redux/tree/master/examples/real-world