Light routes

[xepozz]

Problems

I see errors in the implementation of Route:

• The Route contains a container.
• Route process the Request themselves, i.e. in addition to providing information, they also process it.

What the problems do they make?

• It would seem that having a collection of Route's, it is possible to "dump" (var_dump or other), but this will not work with the current implementation, because the Container will be dumped, in which there are links to the same Route and everything will be repeated in recursion.
• There is no single point of processing Routes. Each Route is independent, but treats itself equally.

Solution

I suggest:

• Return RouterInterface and make an independent Router
• Remove container from Routes
• Remove Request processing from Route
• Process all Routes in the Router
• All middlewars will be initialized in Router too

Current workflow:

$route = new Route('GET', 'home/index');
$response = $route->handle($request);

Working with routes:

Future workflow:

$route1 = new Route('GET', 'home/index');
$route2 = new Route('POST', 'home/index');

$router = new Router($routes); 
// or
$router = $container->get(RouterInterface);
$router->injectRoutes($routes);
// or other ways to create the Router

$response = $router->handle($request);

---

Conclusion

• Now Route can be "dumped", exported or cached very easly.
• Route "knows" no more than what it needs to know. Now it's just a DTO
• A single point of processing all requests (the Router). It gives:
     - The controlled process of matching any routes
     - Now you can implement the storage of the current route being processed
     - Other minor

[samdark]

Decided not to do it for now. May solve debugging issue with __debugInfo().

[samdark]

TODO:

• Implement __debugInfo().