Routing #

Strike uses the powerful and fast symfony/routing component and provides a convenient declaration layer based on the contents of the etc/routes.php file of your application.

Route declaration #

Registering routes #

Routes are registered via the Strike\Framework\Http\Routing\RouteRegistrar. Inside of the etc/routes.php you have access to it via the variable $routes.

Strike provides a fluent interface for declaring routes, by returning the new created route via one of the HTTP verb methods get, head , patch, put and post.

Here are some examples for static routes

// GET endpoint with an invokable controller
$routes->get('/', FrontPageController::class)->setName('frontPage')
// POST endpoint with controller with specified method and additional middleware
$routes->post('/products', [ProductsController::class, 'create'])
    ->setName('product.create')

Route Parameters #

It is a common need to define variable parts in URL's for example to address unique resources. A simple example would be to have an API endpoint to fetch product details via /products/2dbf4527-aea9-43ba-b440-31e02d7de7e2 or /products/wooden-sunglasses.

Here are some examples for routes with parameters

// GET endpoint with a route parameter called id
$routes->get('/products/{id}', [ProductsController::class, 'show'])->setName('product.details')
// PATCH endpoint with a route parameter called id
$routes->patch('/products/{id}', [ProductsController::class, 'update'])->setName('product.update')

Route parameters are passed to the controller as variables with the same name as the parameter. In the above example we have a route parameter called id which will be passed as the second argument of the controller method. More info about route handling can be found in the next chapter.

Route Handling #

Strike can execute controller declared in two different ways.
First one is as array, where the first index is the FQCN of the class and the second index is the name of a public method of that class.
Second one is as string. In this case, the string contains only the FQCN of the class. THe executed method will be the __invoke method.

Request and route parameters #

The executed method on the controller will always receive the current Request as first argument and any potential route parameters as following arguments. The order will be the same as they are declared in the path.

Here an example:

// Route declared like this
$routes->get('/products/{productId}/images/{imageId}/{width}/{length}', ProductImageController::class)
    ->setName('product.images.show')
// Will call the  `__invoke()` ProductImageController
class ProductImageController{
 public function __invoke(Request $request, string $productId, string $imageId, string $width, string $length)
 {
     //...
 }
}