Re:React Router v4 FAQ
by wesleytodd on Friday September 16, 2016 @08:59AM
(#12513657)
We did something similar that uses the Express router: https://github.com/wesleytodd/nighthawk
The one thing we didn't do was layer on top of a flux solution. Seemed more future proof to not tie to anything other than a routing style. If you wanted to do that with our solution it would be as simple as writing an action to do the url change.
Re:React Router v4 FAQ
by tothepixel on Friday September 16, 2016 @11:56AM
(#12514880)
I built a React app for a large Ecom site recently using the same strategy. It handles all URL updates with the History API, and simply AJAX loads the same URL with a query param to hydrate the app with JSON. Works really simply, and doesn't require Redux, Flux, or React Router.
Re:React Router v4 FAQ
by chrisabrams on Friday September 16, 2016 @08:19AM
(#12513485)
Have a link to your router?
Re:React Router v4 FAQ
by antoaravinth on Friday September 16, 2016 @09:19AM
(#12513746)
Sorry, no. However, you can find the same pattern being used in the sound-redux project-https://github.com/andrewngu/sound-redux
Then I have build my own router with `popstate` event and I'm quite happy with it. All the navigation history is pushed to redux. It turns out that it works really well for my needs and application.