Bring back middleware :(

[tptee]

This is the only way to allow consumer middleware to dispatch router actions.

/cc @divmain @baer

[dpwrussell]

Looks good.

Not sure if you want to think about a related problem at the same time though.

I implemented some middleware to do split routes where a request which hits a route with a certain property would be intercepted, the bundle loaded and then on successful load, would replay the action. The problem with this is that it is difficult to access routes or matchRoute from the middleware as the store accessible in the middleware does not have access to these properties.

The only way I've found to do this is to build the middleware with a closure, like this.

const middleware = routes => store => next => action => {
...
}

but then updating the route (Like #88 suggests) is tricky as you'd really need to replace store.routes, but there is no access to store to do that replace and as the routes are a closure and not accessed from the store, even if it was updated, the closure would not change unless that routes was a container object for the actual routes.

Ideas very welcome!

[tptee]

@dpwrussell can you add your comments to #88?

[divmain]

This PR looks good! A pity it is necessary, but ¯\_(ツ)_/¯.