http-kernel VS routing

The compiling of the extension configurations is actually done in a compiler pass. This is called the Merge Pass and is the first compiler pass to be processed. Because of this, once our custom compiler pass reads the configuration of off the extension, we can be sure it is already compiled, cached and ready for use.

I present you the Symfony ControllerEvent, final class, no interface and a boatload of heavy dependencies.

In that regard, someone posted symfony's test suite as an example of good PHPUnit testing. The first file I clicked on demonstrated how worthless (IMO) unit testing can be: https://github.com/symfony/http-kernel/blob/v6.0.8/Tests/CacheClearer/ChainCacheClearerTest.php

The second one was in the Symfony HTTP kernel which is managed by Composer. That file contains this line:

You can also define routes in the method directly:

Check this out: stand-alone Symfony routing

Here is a simple routing project from a few years ago that should still work. It shows how to use controller annotations to define routes. In particular it show some of the basic startup code needed for the router.

After looking through Stackoverflow a bit, I found this test repo as well, it might help: https://github.com/cerad/routing

Here is a simple example that worked the last time I checked it. I was actually looking at how to use controller annotations for routing which turns out to be more painful than expected. But you should be able to replace the annotation loader with a php route loader with minimal effort.