[WIP] Add routerPath to Context

[schwarmco]

Fixes #34

Though, the ctx._matchedRoute fails when handling middleware-chains, i'd go with introducing ctx.routerPath instead of replacing it to be consistent with ctx.routerName and to not break backwardscompatibility(?).

To note is, that a Middleware can only know about the "correct" route, after it was hit. This means:

// this does not work
const middleware = async function (ctx, next) {
  expect(ctx.routerPath).to.be('/users/list');
  return next();
};
router.use(middleware);

// this works
const middleware = async function (ctx, next) {
  await next();
  expect(ctx.routerPath).to.be('/users/list');
};
router.use(middleware);

[schwarmco]

Just found out, there's already a router-option called routerPath. Based on if we want to "break" ctx._matchedRoute i can use either that or come up with a new name for it to avoid confusion.

[schwarmco]

I renamed it to ctx.matchedRoute now - maybe you can have a look @niftylettuce ?

There are these two things, which probably reflect the same feature, but work different:

router/lib/router.js

Lines 355 to 359 in 6131069

	const mostSpecificLayer = matchedLayers[matchedLayers.length - 1]
	ctx._matchedRoute = mostSpecificLayer.path;
	if (mostSpecificLayer.name) {
	ctx._matchedRouteName = mostSpecificLayer.name;
	}

router/lib/router.js

Line 365 in 6131069

ctx.routerName = layer.name;

[kroleg]

@schwarmco #34 was just fixed by #93, so i assume this one can be closed

[niftylettuce]

@koa/router v9.1.0 released to npm and mirrored to koa-router as well

https://github.com/koajs/router/releases/tag/v9.1.0