James Gillmore

in addition I think Storybook should be what you use ALL THE TIME. It loads your app faster when you only need to parse and render part of your codebase....

+1 For me the primary need is to be able to define rest arguments as tuples. Rest inside tuples seems a lot more complex of a feature to add and...

@bfillmer again, great article! Gave me some ideas. I haven't used Sagas in a while, but I loved them when I did, so I'm not sure of the correct terminology....

@bfillmer yea pretty much--kill the hash. I very much have enjoyed sagas when I've worked with them. It's obvious they resonated with a large # of Redux developers. You hardly...

I don't. I worry about marketing. There's a million great things that have been built with 1000 stars (most of which by the way are now outdated and no longer...

As far as implementation, that's where the *bloat* potential is. Obviously the best implementation involves kicking off a saga within RFR itself. That we cannot do, as we can't include...

```js import createHistory from 'history/createBrowserHistory' import { connectRoutes } from 'redux-first-router' import createSagaWithRouting from 'redux-first-router-saga' import { ROUTE_HOME, ROUTE_ABOUT } from 'types' import { homeSaga } from 'state/sagas/home' import mainSaga...

so bottom line is we make it a plugin package (of which we have several that function exactly like that is, i.e. as an option). That means we dont have...

I dont suppose u can show me how to do it. it's a blind spot of mine and I never fully understood the problem.

I guess its just something like this: ```js export default function createMainSaga(mainSaga) { return function mainSaga(routeTypeSelector, routesMap, initialDispatch) { *function routesSaga () { yield put(initialDispatch()) const initialRoute = yield select(routeTypeSelector)...