Michelle Tilley

I'm [not sure a route store is really the correct technique in most cases](http://stackoverflow.com/a/23636491/62082); the React Router example in the Fluxxor docs utilizes it mainly because models are _not_ created...

In React Router 1.0 RC1, [they show how you can get the `history` object](https://github.com/rackt/react-router/blob/master/UPGRADE_GUIDE.md#locations): > ### Locations > > Locations are now called histories (that emit locations). You import >...

I haven't done a whole lot of work with web workers, but the idea is very interesting. I'll do some research and see what this might look like. (Any tips...

Hey, @manuelmazzuola, thanks for the info! One additional note, with React Router 1.0 RC1, you can use the new `createElement` router prop to simplify getting the `flux` instance to your...

@PendletonJones I'll definitely get the example in once React Router 1.0 comes out of release candidate status. In the meantime take a look at #141 if you're still having issues...

Hi, @zdila, There are still some differing opinions on this. The "route store" idea is fairly popular, and I'd probably recommend that if you wanted to "stay fluxy" (so basically...

Good catch! This is definitely something I want to support, but an initial pass seems to indicate it may not be super straightforward because of the way React handles non-hook...

Hi again. :) This is going to be another opinionated answer, as flux really only talks about data _flow_, and not really the shape or access of that data. If...

Ideally, the components that touch flux should be minimal and only pass data/callbacks into more functionally pure components (these top-level, flux-referencing components are referred to as "Containers" in [this talk](https://www.youtube.com/watch?v=KYzlpRvWZ6c&t=1351))....

Perfect, thanks, this helps make things much more concrete. To start with, you can't really "unit test" that clicking the component turns it green—this involves multiple units (the flux action,...