Routing

Marko uses PHP attributes to define routes directly on controller methods. No separate route files, no registration boilerplate.

Defining Routes

app/blog/Controller/PostController.php

<?php

declare(strict_types=1);

namespace App\Blog\Controller;

use Marko\Routing\Attributes\Get;
use Marko\Routing\Attributes\Post;
use Marko\Routing\Attributes\Delete;
use Marko\Routing\Http\Response;

class PostController
{
    #[Get('/posts')]
    public function index(): Response
    {
        return Response::json(data: ['posts' => []]);
    }

    #[Get('/posts/{id}')]
    public function show(int $id): Response
    {
        return Response::json(data: ['id' => $id]);
    }

    #[Post('/posts')]
    public function store(): Response
    {
        return Response::json(data: ['created' => true], statusCode: 201);
    }

    #[Delete('/posts/{id}')]
    public function destroy(int $id): Response
    {
        return Response::json(data: [], statusCode: 204);
    }
}

Available HTTP Method Attributes

Attribute	HTTP Method
#[Get]	GET
#[Post]	POST
#[Put]	PUT
#[Patch]	PATCH
#[Delete]	DELETE

Route Parameters

Parameters in {braces} are automatically injected into the method by name:

#[Get('/users/{userId}/posts/{postId}')]
public function show(int $userId, int $postId): Response
{
    // $userId and $postId are extracted from the URL
}

Middleware

Apply middleware to routes using the #[Middleware] attribute:

use Marko\Routing\Attributes\Get;
use Marko\Routing\Attributes\Middleware;
use Marko\Authentication\Middleware\AuthMiddleware;

class AdminController
{
    #[Get('/admin/dashboard')]
    #[Middleware(AuthMiddleware::class)]
    public function dashboard(): Response
    {
        // Only authenticated users reach this
    }
}

Multiple Middleware

#[Get('/admin/settings')]
#[Middleware(AuthMiddleware::class)]
#[Middleware(AdminRoleMiddleware::class)]
public function settings(): Response
{
    // Must be authenticated AND have admin role
}

Route Conflict Detection

Marko detects route conflicts at boot time, not at request time. If two controllers register the same path and method, you get a loud error immediately — not a mysterious 404 in production.

Route Overrides

Higher-priority modules can override routes from lower-priority modules. If a vendor package defines GET /posts and your app/blog also defines GET /posts, your version wins.

Disabling Routes

To remove a vendor route without replacing it, use the #[DisableRoute] attribute. Place it on a method that also has the route attribute you want to disable --- #[DisableRoute] takes no parameters and simply disables the route defined by the preceding routing attribute:

use Marko\Routing\Attributes\Get;
use Marko\Routing\Attributes\DisableRoute;

class BlogRouteOverrides
{
    #[Get('/blog/rss')]
    #[DisableRoute]
    public function disableRss(): void {}
}

Creating Middleware

Middleware implements MiddlewareInterface:

app/myapp/Middleware/RateLimitMiddleware.php

<?php

declare(strict_types=1);

namespace App\MyApp\Middleware;

use Marko\Routing\Http\Request;
use Marko\Routing\Http\Response;
use Marko\Routing\Middleware\MiddlewareInterface;

class RateLimitMiddleware implements MiddlewareInterface
{
    public function handle(
        Request $request,
        callable $next,
    ): Response {
        // Before the controller
        $this->checkRateLimit($request);

        // Call the next middleware or controller
        return $next($request);
    }
}

Next Steps

• Database — persist and query data
• Authentication — protect routes
• Middleware deep dive — how plugins compare to middleware
• Routing package reference — full API details