req.params gets over written on each route so a middleware app can't modify them as they are passed to the next route.
Here is a patch file that fixes this issue:
there could be more/less params for the following route though
True, but at the moment, that wouldn't happen either, since each route processed over writes all the other params..
We would add a mix there to mix the two together..
The end issue being that middleware can't change it ;)
hmm wonder if we should handle this in express, since this is with the route-specific middleware right?
I thought about doing that, but the route statically connects those params on each iteration. It just seems like the right place to put it, since middleware is middleware.
hmm not sure how i feel about it, nothing stands out to me as far as it being some sort of gotcha, but seems like it could potentially be an issue in some cases