support for matrix parameters when routing

[koulmomo]

Here is an issue on another project that has a nice explanation of what matrix parameters are as well as a StackOverflow question explaining their usefulness.
Only referencing them since I myself had only just recently learned about them.

I am not looking for a comprehensive solution to fully support matrix parameters in express (by perhaps aggregating them in a req.matrix object). For now I'd settle for a having the express routing support correctly matching paths with matrix params with their handlers.

The expected behavior I am hoping for:

using the app generated by the express-generator

/users;foo=bar should not 404 and instead map to the handler for /users

If there are absolutely no plans to support matrix parameters, it would be nice to have a warning or explicitly declaring it in the routing section of the docs.

Thanks!

[dougwilson]

I doubt we would support this in the default router. This can very easily be implemented as a third-party router, though.

Asking us to list that "we don't support matrix routing" is not viable--if we list what types of routing we don't support, the list will be endless. Instead we list what we support, so if we don't say we support matrix routing, it means we don't support it.

If the third-party express router that supports matrix parameters get enough traction, then we can consider adding to core, but otherwise, it is much more suitable as a third-party router.

[dougwilson]

I can always reconsider if someone submits an extremely well-tested implementation, preferably to the "router" module on npm, which express is switching to use.

[dougwilson]

Any traction on creating a PR to here or (more preferred) the router npm module?