README

This is a library with additional classes for usage in combination with the Symfony framework.

Mailer helpers

Automatically set a sender address

We want to replace setting the sender via mailer.yaml as envelope (@see https://symfonycasts.com/screencast/mailer/event-global-recipients) as this would still require each mail to have a FROM address set and also doesn't allow us to set a sender name.

config/services.yaml:

    Vrok\SymfonyAddons\EventSubscriber\AutoSenderSubscriber:
        arguments:
            $sender: "%env(MAILER_SENDER)%"

.env[.local]:

MAILER_SENDER="Change Me <your@email>"

Messenger helpers

Resetting the logger before/after a message

We want to group all log entries belonging to a single message to be grouped with a distinct UID and to flush a buffer logger after a message was processed (successfully or failed), to immediately see the entries in the log:

config/services.yaml:

    # add a UID to the context, same UID for each HTTP request or console command
    # and with the event subscriber also for each message 
    Monolog\Processor\UidProcessor:
        tags:
            - { name: monolog.processor, handler: logstash }

    # resets the UID when a message is received, flushed a buffer after a
    # message was handled. Add this multiple times if you want to flush more
    # channels, e.g. messenger
    app.event.reset_app_logger:
        class: Vrok\SymfonyAddons\EventSubscriber\ResetLoggerSubscriber
        tags:
            - { name: monolog.logger, channel: app }

Validators

AtLeastOneOf

Works like Symfony's own AtLeastOneOf constraint, but instead of returning a message like This value should satisfy at least ... it returns the message of the last failed validation. Can be used for obviously optional form fields where only simple messages should be displayed when AtLeastOne is used with Blank as first constraint. See AtLeastOneOfValidatorTest for examples.

NoHtml

This validator tries to detect if a string contains HTML, to allow only plain text. See NoHtmlValidatorTest for examples of allowed / forbidden values.

NoLineBreak

This validator raises a violation if it detects one or more linebreak characters in the validated string. Detects unicode linebreaks, see NoLineBreaksValidatorTest for details.

NoSurroundingWhitespace

This validator raises a violation if it detects trailing or leading whitespace or newline characters in the validated string. Linebreaks and spaces are valid within the string. Uses a regex looking for \s and \R, see NoSurroundingWhitespaceValidatorTest for details on detected characters.

PasswordStrength

This validator evaluates the strength of a given password string by determining its entropy instead of requireing something like "must contain at least one uppercase & one digit & one special char". Allows to set a minStrength to vary the requirements. See Vrok\SymfonyAddons\Helper\PasswordStrength for details on the calculation.

PHPUnit helpers

Using the ApiPlatformTestCase

This class is used to test ApiPlatform endpoints by specifying input data and verifying the response data. It combines the traits documented below to refresh the database before each test, optionally create authenticated requests and check for created logs / sent emails / dispatched messages. It allows to easily check for expected response content, allowed or forbidden keys in the data or to verify against a given schema.

Requires "symfony/browser-kit" & "symfony/http-client" to be installed (and of cause ApiPlatform).

<?php

use Vrok\SymfonyAddons\PHPUnit\ApiPlatformTestCase;

class AuthApiTest extends ApiPlatformTestCase
{
    public function testAuthRequiresPassword(): void
    {
        $this->testOperation([
            'uri'            => '/authentication_token',
            'method'         => 'POST',
            'requestOptions' => ['json' => ['username' => 'fakeuser']],
            'responseCode'   => 400,
            'contentType'    => 'application/json',
            'json'           => [
                'type'   => 'https://tools.ietf.org/html/rfc2616#section-10',
                'title'  => 'An error occurred',
                'detail' => 'The key "password" must be provided.',
            ],
        ]);
    }
}

Option	Usage	Example
prepare	Callable, to be executed _after_ the kernel was booted and the DB refreshed, but _before_ the request is made	'prepare' => static function (ContainerInterface $container, array &$params): void { $em = $container->get('doctrine')->getManager(); $log = new ActionLog(); $log->action = ActionLog::FAILED_LOGIN; $log->ipAddress = '127.0.0.1'; $em->persist($log); $em->flush(); $params['requestOptions']['query']['id'] = $log->id; }
uri	the URI / endpoint to call	`'uri' => '/users'`
iri	an array of `[classname, [field => value]]` that is used to fetch a record from the database, determine its IRI, which is then used as URI for the request	`'iri' => [User::class, [email => 'test@test.de']]`
email	if given, tries to find a User with that email and sends the request authenticated as this user with lexikJWT bundle	`'email' => 'test@test.de'`
postFormAuth	if given (and 'email' is set) the JWT from Lexik is sent as 'application/x-www-form-urlencoded' request in a form field. This is used for download endpoints where the browser should present the user with the file to download instead of loading it into memory via Javascript. (As we don't want to supply the token via GET to prevent security issues and as we cannot set a cookie.)	`'postFormAuth' => 'bearer'`
method	HTTP method for the request, defaults to GET. If PATCH is used, the content-type header is automatically set to `application/merge-patch+json` (if not already specified)	`'method' => 'POST'`
requestOptions	options for the HTTP client, e.g. query parameters or basic auth	'requestOptions' => [ 'json' => [ 'username' => 'Peter', 'email' => 'peter@example.com', ], // or: 'query' => [ 'order' => ['createdAt' => 'asc'], ], // or: 'headers' => ['content-type' => 'application/json'], ]
files	An array of one or more files to upload. The files will be copied to a temp file, and wrapped in an `UploadedFile`, so the tested application can move/delete it as it needs to. If this option is used, the content-type header is automatically set to `multipart/form-data` (if not already specified)	'files' => [ 'picture' => [ 'path' => '/path/to/file.png', 'originalName' => 'mypicture.png', 'mimeType' => 'image/png', ] ]
responseCode	asserts that the received status code matches	`'responseCode' => 201`
contentType	asserts that the received content type header matches	`'contentType' => 'application/ld+json; charset=utf-8'`
json	asserts that the returned content is JSON and contains the given array as subset	'json' => [ 'username' => 'Peter', 'email' => 'peter@example.com', ]
requiredKeys	asserts the dataset contains the list of keys. Used for elements where the value is not known in advance, e.g. ID, slug, timestamps. Can be nested.	'requiredKeys' => ['hydra:member'][0]['id', '@id']
forbiddenKeys	like requiredKeys, but the dataset may not contain those	'forbiddenKeys' => ['hydra:member'][0]['password', 'salt']
schemaClass	Asserts that the received response matches the JSON schema for the given class. If the `iri` parameter is used or the request method is not GET, the item schema is used. Else the collection schema is used.	'schemaClass' => User::class,
createdLogs	array of entries, asserts the messages to be present (with the correct log level) in the monolog handlers after the operation ran	'createdLogs' => [ ['Failed to validate the provider', Level::Error], ],
emailCount	asserts this number of emails to be sent via the mailer after the operation was executed	'emailCount' => 2,
messageCount	asserts this number of messages to be dispatched to the message bus	'messageCount' => 2,
dispatchedMessages	Array of message classes, asserts that at least one instance of each given class has been dispatched to the message bus. An Element can also be an array of [FQCN, callable], in that case the callback is called for each matching message with that message as first parameter and the JSON response as second parameter, to trigger additional assertions for the message.	'dispatchedMessages' => [ TenantCreatedMessage::class, [TenantCreatedMessage::class, function (object $message, array $data): void { self::assertSame($data['id'], $message->tenantId); }] ],
dispatchedEvents	Array of event names (may be class names), asserts that at least one instance of each given event has been dispatched to Symfony's EventDispatcher.	'dispatchedEvents' => [ 'kernel.response', ProjectPreCreateEvent::class, ],

Using the RefreshDatabaseTrait

(Re-)Creates the DB schema for each test, removes existing data and fills the tables with predefined fixtures. Install doctrine/doctrine-fixtures-bundle and create fixtures, the trait uses the test group per default.

Just include the trait in your testcase and call bootKernel() or createClient(), e.g. in the setUp method:

use Symfony\Bundle\FrameworkBundle\Test\KernelTestCase;
use Vrok\SymfonyAddons\PHPUnit\RefreshDatabaseTrait;

class DatabaseTest extends KernelTestCase
{
    use RefreshDatabaseTrait;

    /**
     * @var \Doctrine\ORM\EntityManager
     */
    private $entityManager;

    protected function setUp(): void
    {
        $kernel = self::bootKernel();

        $this->entityManager = $kernel->getContainer()
            ->get('doctrine')
            ->getManager();
    }

}

Optionally define which fixtures to use for this test class:

protected static $fixtureGroups = ['test', 'other'];

Supports setting the cleanup method after tests via DB_CLEANUP_METHOD. Allowed values are purge, dropSchema and dropDatabase, for more details see RefreshDatabaseTrait::$cleanupMethod. Suggested method is purge for all database platforms, see benchmark below. Results may vary depending on your DB schema and/or server setup, so check if different settings work better for you.

On MySQL/MariaDB you can switch the purge method, by setting the ENV DB_PURGE_MODE to delete (the default) or truncate. For details the the trait class. This setting has no effect on the other platforms.

Benchmark

The numbers below come from the Refresh Benchmark CI workflow (see bin/benchmark.sh): Median milliseconds per bootKernel() over 200 boots per cell, on a GitHub-hosted ubuntu-latest runner (4 CPU, 15 GB RAM), against this package's own 14 entity test schema.

platform	on tmpfs				on disk
	purge		dropSchema	dropDatabase	purge		dropSchema	dropDatabase
	delete	truncate	dropSchema	dropDatabase	delete	truncate	dropSchema	dropDatabase
SQLite	7.4		19.7	12.0	53.3		153.9	64.9
MariaDB 12	12.1	13.1	37.5	25.9	107.4	54.8	412.2	376.5
MySQL 9	23.4	25.1	77.3	61.9	121.0	309.4	753.2	521.6
PostgreSQL 18	23.4		68.3	78.5	35.5		162.9	186.1
SQL Server 2022	16.1		120.2	dnf *	40.0		312.2	dnf *

Every value is milliseconds per refresh. The bold cell of each row is the fastest method on tmpfs, which is the setup worth having; the disk columns are what you pay for not having it.
dnf: did not finish in the benchmark's limit of 600s per run.

DB_PURGE_MODE only has an effect on MySQL and MariaDB. On the other three platforms both purge modes run the same code, so their two columns are merged and show the mean of the two runs. How far those two runs sat apart is a useful reading of its own: 0.2 ms on SQLite, but 31.5 against 39.5 ms on PostgreSQL, so differences of that order between neighbouring cells are noise, not a result.

DB_CLEANUP_METHOD=purge is usually the cheapest method everywhere, the DB_PURGE_MODE then varies
Putting the database on tmpfs is worth far more than the choice of cleanup method. Other optimizations
Using further optimizations like --innodb-doublewrite=OFF --innodb-flush-log-at-trx-commit=2 --skip-log-bin for MySQL/MariaDB, -c fsync=off -c synchronous_commit=off -c full_page_writes=offfor PostgreSQL or ALTER DATABASE model SET DELAYED_DURABILITY = FORCED for SQL Server produce no better results or perform even worse, so check before using them

Running the databases on tmpfs

Test databases are throwaway by definition, so there is no reason to write them to disk. This is the single largest speedup available and costs nothing but a few lines.

With docker compose:

services:
  mysql:
    image: mysql:9
    tmpfs:
      - /var/lib/mysql:rw,size=2g

  mariadb:
    image: mariadb:12
    tmpfs:
      - /var/lib/mysql:rw,size=2g

  postgres:
    image: postgres:18
    tmpfs:
      - /var/lib/postgresql/18/docker:rw,size=2g

  mssql:
    image: kcollins/mssql:latest
    tmpfs:
      - /var/opt/mssql/data:rw,size=2g

In GitHub Actions, a service container takes no command, and options are passed to docker create, so --tmpfs belongs there:

    services:
      mysql:
        image: mysql:9
        env:
          MYSQL_ROOT_PASSWORD: root
          MYSQL_DATABASE: db_test
        options: >-
          --tmpfs /var/lib/mysql:rw,size=2g
          --health-cmd="mysqladmin ping"
          --health-interval=10s
          --health-timeout=5s
          --health-retries=5
        ports:
          - 3306:3306

For SQLite, point the DSN at a tmpfs path instead, e.g. sqlite:////dev/shm/test.db — four slashes, three would make the path relative.

Using the MonologAssertsTrait

For use with an Symfony project using the monolog-bundle. Requires monolog/monolog of v3.0 or higher.

Include the trait in your testcase and call prepareLogger before triggering the action that should create logs and use assertLoggerHasMessage afterwards to check if a log record was created with the given message & severity:

use Monolog\Level;
use Psr\Log\LoggerInterface;
use Symfony\Bundle\FrameworkBundle\Test\KernelTestCase;
use Vrok\SymfonyAddons\PHPUnit\MonologAssertsTrait;

class LoggerTest extends KernelTestCase
{
   use MonologAssertsTrait;

   public function testLog(): void
   {      
       self::prepareLogger();

       $logger = static::getContainer()->get(LoggerInterface::class);
       $logger->error('Failed to do something');
       
       self::assertLoggerHasMessage('Failed to do something', Level::Error);
   }
}

Workflow helpers

Require symfony/workflow.

PropertyMarkingStore

Can be used instead of the default MethodMarkingStore, for entities & properties without Setter/Getter.

workflow.yaml:

framework:
  workflows:
    application_state:
      type: state_machine
      marking_store:
        # We need to use a service as there is no option to register a new "type"
        service: workflow.application.marking_store

services.yaml:

    # When using the "service" option, all other settings like "property: state"
    # are ignored in the workflow.yaml -> That's why we need a service definition
    # with the correct arguments.
    workflow.application.marking_store:
      class: Vrok\SymfonyAddons\Workflow\PropertyMarkingStore
      arguments: [true, 'state']

WorkflowHelper

Allows to get an array of available transitions and their blockers, can be used to show the user what transitions are possible from the current state and/or why a transition is currently blocked.

    public function __invoke(
        Entity $data
        WorkflowInterface $entityStateMachine,
    ): array
    {
      $result = $data->toArray();
      
      $result['transitions'] = WorkflowHelper::getTransitionList($data, $entityStateMachine);
      
      return $result;
    }

'publish' => [
    'blockers' => [
        TransitionBlocker::UNKNOWN => 'Title is empty!',
    ],
],

Cron events

Adding this bundle to the bundles.php registers three new CLI commands:

    Vrok\SymfonyAddons\VrokSymfonyAddonsBundle::class => ['all' => true],

bin/console cron:hourly
bin/console cron:daily
bin/console cron:monthly

When these are called, they trigger an event (CronHourlyEvent, CronDailyEvent, CronMonthlyEvent) that can be used by one ore more event listeners/subscribers to do maintenance, push messages to the messenger etc. It is your responsibility to execute these commands via crontab correctly!

use Vrok\SymfonyAddons\Event\CronDailyEvent;

class MyEventSubscriber implements EventSubscriberInterface
    public static function getSubscribedEvents(): array
    {
        return [
            CronDailyEvent::class => [
                ['onCronDaily', 100],
            ],
        ];
    }
}

ApiPlatform Filters

SimpleSearchFilter

Selects entities where the search term is found (case insensitive) in at least one of the specified properties. The properties can also be of relations, e.g. child.name. All specified properties must be string types (varchar, text etc.) or JSON fields (Postgres only), in that case the JSON is cast to string first.

#[ApiFilter(
    filterClass: SimpleSearchFilter::class,
    properties: [
        'description',
        'name',
        'slug',
        'parent.title',
        'children.content',
    ],
    arguments: ['searchParameterName' => 'pattern']
)]

Requires CAST as defined Doctrine function, e.g. by vrok/doctrine-addons:

doctrine:
  orm:
    dql:
      string_functions:
        CAST: Vrok\DoctrineAddons\ORM\Query\AST\CastFunction

ContainsFilter

Postgres-only: Filters entities by their jsonb fields, if they contain the search parameter, using the @> operator. For example for filtering for numbers in an array.

#[ApiFilter(filterClass: ContainsFilter::class, properties: ['numbers'])]

Requires CONTAINS as defined Doctrine function, provided by vrok/doctrine-addons:

doctrine:
  orm:
    dql:
      string_functions:
        CONTAINS: Vrok\DoctrineAddons\ORM\Query\AST\ContainsFunction

JsonExistsFilter

Postgres-only: Filters entities by their jsonb fields, if they contain the search parameter, using the ? operator. For example for filtering Users by their role, to prevent accidental matching with overlapping role names (e.g. ROLE_ADMIN and ROLE_ADMIN_BLOG) when searching as text with WHERE roles LIKE '%ROLE_ADMIN%'.

#[ApiFilter(filterClass: JsonExistsFilter::class, properties: ['roles'])]

Requires JSON_CONTAINS_TEXT as defined Doctrine function, provided by vrok/doctrine-addons:

doctrine:
  orm:
    dql:
      string_functions:
        JSON_CONTAINS_TEXT: Vrok\DoctrineAddons\ORM\Query\AST\JsonContainsTextFunction

MultipartDecoder

Adding this bundle to the bundles.php registers the MultipartDecoder to allow handling of file uploads with additional data (e.g. in ApiPlatform):

    Vrok\SymfonyAddons\VrokSymfonyAddonsBundle::class => ['all' => true],

The decoder is automatically called for multipart requests and simply returns all POST parameters and uploaded files together. To enable this add the multipart format to your config\api_platform.yaml:

api_platform:
    formats:
        multipart: ['multipart/form-data']

FormDecoder

Adding this bundle to the bundles.php registers the FormDecoder to allow handling HTML form data in ApiPlatform:

    Vrok\SymfonyAddons\VrokSymfonyAddonsBundle::class => ['all' => true],

The decoder is automatically called for form requests and simply returns all POST parameters. To enable this add the form format to your config\api_platform.yaml:

api_platform:
    formats:
      form: ['application/x-www-form-urlencoded']

Twig Extensions

Adding this bundle to the bundles.php together with the symfony/twig-bundle registers the new extension:

    Vrok\SymfonyAddons\VrokSymfonyAddonsBundle::class => ['all' => true],

FormatBytes

Converts bytes to human-readable notation (supports up to TiB). This extension is auto-registered. In your Twig template:

  {{ attachment.filesize|formatBytes }}

Outputs: 9.34 MiB

Experimental / Additional Features

NamedArgumentsFromArrayRector

This Rector allows migrating function calls that previously used an array of options (like ApiPlatformTestCase#testOperation) to use named arguments instead.

This can be configured to target static functions, static class methods or instance methods. Example for the rector.php:

use Vrok\SymfonyAddons\Rector\NamedArgumentsFromArrayRector;

return RectorConfig::configure()
    ->withConfiguredRule(NamedArgumentsFromArrayRector::class, [
        'targets' => [
            [ApiPlatformTestCase::class, 'testOperation'],
        ],
    ])
;

This converts

$this->testOperation([
    'uri' => '/test',
    'requiredKeys' => [
        'success',
        'message',
    ],
    'dispatchedEvents' => ['failedEvent'],
]);

$this->testOperation(uri: '/test', requiredKeys: [
    'success',
    'message',
], dispatchedEvents: ['failedEvent']);

Attention: This Rector is not yet unit-tested, please report any bugs you find!

WrapNamedMethodArgumentsFixer

This Fixer for php-cs-fixer allows wrapping long lines of function calls with named arguments to contain one argument per line, respecting multiline argument values like arrays. This can be used to improve readability, e.g. after using the NamedArgumentsFromArrayRector which puts multiple arguments on the same line.

It allows configuring the maximum number of arguments to keep on a single line, each call with more named arguments will be wrapped.

return $config
    ->registerCustomFixers([
        new Vrok\SymfonyAddons\PhpCsFixer\WrapNamedMethodArgumentsFixer(),
    ])
    ->setRules([
        "VrokSymfonyAddons/wrap_named_method_arguments" => [
            'max_arguments' => 2,
        ],

        // your custom formatting rules:
        '@Symfony'               => true,
        [...]
    ])
;