Symfony Playgound with its Container and a custom configuration

test.php

<?php

use App\Kernel;

require __DIR__.'/vendor/autoload_runtime.php';

use Symfony\Component\Console\Output\StreamOutput;
use Symfony\Component\DependencyInjection\Compiler\CompilerPassInterface;
use Symfony\Component\DependencyInjection\ContainerBuilder;

return function () {
    $k = new class('dev', true) extends Kernel implements CompilerPassInterface {
        public function process(ContainerBuilder $container)
        {
            $container->getAlias('logger')->setPublic(true);
            $container->getDefinition('monolog.handler.console')->setPublic(true);
        }
    };
    $k->boot();
    $c = $k->getContainer();

    $c->get('monolog.handler.console')->setOutput(
        new StreamOutput(fopen('php://stdout', 'w'),
        StreamOutput::VERBOSITY_VERY_VERBOSE,
    ));

    $logger = $c->get('logger');
    $em = $c->get('doctrine.orm.entity_manager');

    // Start of playground
};

cool. 👏

Sorry my stupidity, but what is for?

I often need to test "something" in my application, and it helps me to test that thing.

For example

• Do I setup my CASCADE relation in the good direction : what does happen when I delete a project, does it also delete the organization
• How does my Doctrine type behave if my column is empty
• etc

It could be also solved with

• an integration test
• a custom debug command
• a custom debug controller
• etc.

But I have this habit for a very long time, and I like to be able to "hack" and prototype quickly. So in almost every projects I work on have this test.php file.

Oh ok, gotcha you.

Very good! Thanks you.
It is worth mentioning that this command can be executed using symfony php test.php