By default, this bundle registers server middleware by finding all services with the babdev.websocket_server.server_middleware tag and sorting them by priority.

Below is the list of middleware provided by this bundle and the library and their default priorities:

New middleware should be added with a priority lower than 0 as the BabDev\WebSocket\Server\WAMP\Middleware\DispatchMessageToHandler middleware should be the last middleware in the stack.

Middleware must have the decorated middleware as the first parameter in the constructor, and cannot use a named parameter in the service definition (i.e. $middleware: !abstract decorated middleware for YAML); this is required for the compiler pass which builds the middleware stack to correctly set the arguments.

Because priorities must be specified, this bundle does not provide autoconfiguration of the BabDev\WebSocket\Server\ServerMiddleware interface to the babdev.websocket_server.server_middleware tag, so services will have to be manually tagged. This can be done with either explicit configuration in your container configuration files, or if you are using autowiring, the #[Autoconfigure] attribute on your middleware class.

# config/services.yaml
services:
    App\WebSocket\Middleware\EarlyMiddleware:
        arguments:
            - !abstract decorated middleware
        tags:
            - { name: babdev.websocket_server.server_middleware, priority: -75 }

<?php declare(strict_types=1);

namespace App\WebSocket\Middleware;

use BabDev\WebSocket\Server\ServerMiddleware;
use Symfony\Component\DependencyInjection\Attribute\Autoconfigure;

#[Autoconfigure(tags: [['babdev.websocket_server.server_middleware' => ['priority' => -75]]])]
final class EarlyMiddleware implements ServerMiddleware
{
    public function __construct(
        private readonly ServerMiddleware $middleware,
    ) {
    }

    /* Class implementation */
}