If you are designing an API or an expandable application, grouping the application routes by the pipe will improve your application's performance.

For example, when creating a data path called users/, a pipe combines the attributes of this group on the url.

$pipe = new Pipe('users/', [App\Middleware\Dummy::class], '<str:name>.router');
$pipe->add('test', new Route('GET', '/test', 'App\Controller\DefaultController::test'));

As long as the http request users/ does not exist, the preg_match operation is not applied to the routes of this object, and performance will be improved because your application is fragmented.

$collection = new RouteCollection($config);

$collection->add('home', new Route('GET', '/', 'App\Controller\DefaultController::index'));

$pipe = new Pipe('users/example/', [App\Middleware\Dummy::class], '<str:name>.router');
$pipe->add('dummy', new Route('GET', '/<int:id>/<str:name', 'App\Controller\DefaultController::test'));

Testing the values of an added route;

$route = $collection->get('users/example/dummy');

echo $route->getHandler(); //  "App\Controller\DefaultController::test"
echo $route->getMethods()[0]; // GET
echo $route->getPattern(); //  "/users/example/(?\d+)/(?\w+)"

Using pipes in .yaml files

If the last character of the highest level rule ends with a forward slash /, this rule is treated as a pipe.

        - App\Middleware\Dummy
        path: /<int:id>/<str:name>
        handler: App\Controller\DefaultController::test