http-kernel
Our great sponsors
routing | http-kernel | |
---|---|---|
4 | 6 | |
5 | 8,040 | |
- | 0.3% | |
0.0 | 9.2 | |
about 1 year ago | 11 days ago | |
PHP | PHP | |
- | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
routing
-
Github link to legacy PHP custom app, which uses Symfony routing component only?
Check this out: stand-alone Symfony routing
-
How to use just the Symfony Router
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.
-
Legacy "Routing" with PHP 8.1
After looking through Stackoverflow a bit, I found this test repo as well, it might help: https://github.com/cerad/routing
-
How to create a basic Symfony app with 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.
http-kernel
-
Reading bundle configuration inside Symfony Compiler Passes
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.
-
95% final readonly classes. What is your superpower?
I present you the Symfony ControllerEvent, final class, no interface and a boatload of heavy dependencies.
-
How do you test your code ?
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
-
What to do when it is necessary to modify code in a library managed by a package manager?
The second one was in the Symfony HTTP kernel which is managed by Composer. That file contains this line:
-
How to create a basic Symfony app with routing?
You can also define routes in the method directly:
What are some alternatives?
http-foundation - Defines an object-oriented layer for the HTTP specification
console - Eases the creation of beautiful and testable command line interfaces
translation - Provides tools to internationalize your application
event-dispatcher - Provides tools that allow your application components to communicate with each other by dispatching events and listening to them
Guzzle - Guzzle, an extensible PHP HTTP client
routing - Maps an HTTP request to a set of configuration variables
process - Executes commands in sub-processes
Pest - Pest is an elegant PHP testing Framework with a focus on simplicity, meticulously designed to bring back the joy of testing in PHP.
cache - Provides extended PSR-6, PSR-16 (and tags) implementations
filesystem - Provides basic utilities for the filesystem
polyfill-mbstring - Symfony polyfill for the Mbstring extension
Amazon Web Service SDK - Official repository of the AWS SDK for PHP (@awsforphp)