Contributed by
Alexander M. Turek
in #47916
and #47943.
In your Symfony applications you probably have a configuration similar to the following:
# config/routes.yaml
controllers:
resource: ../src/Controller/
type: attribute
This tells Symfony to look for all PHP files defined in that directory and load the routes defined as PHP attributes in the classes of those files. Internally, this uses AnnotationDirectoryLoader and AnnotationFileLoader to find the route annotations.
More specifically, AnnotationFileLoader
finds all PHP files recursively and
AnnotationFileLoader
inspects their contents, using PHP token_get_all()
function, to get the full class name for the first class found in the file.
The entire process is cached, so it only impacts performance the first time.
However, since all modern PHP projects use PSR-4 class autoloading, all this is unnecessary. PSR-4 defines the corresponding file path for a given fully qualified class name (and vice versa), so there's no need to guess which class defines each file.
In Symfony 6.2, we're introducing a new PSR-4 routing loader, which is similar to the annotation routing loader, but finds routes faster because it assumes that your project files follow PSR-4. See Psr4DirectoryLoader code.
The only needed change in your applications is to define the PSR-4 namespace used by your controller classes:
# config/routes.yaml
controllers:
- resource: ../src/Controller/
+ resource:
+ path: ../src/Controller/
+ namespace: App\Controller
type: attribute
In addition to the YAML configuration shown above, the namespace
option is
also supported in XML and PHP configs.
<hr style="margin-bottom: 5px" />
<div style="font-size: 90%">
<a href="https://symfony.com/sponsor">Sponsor</a> the Symfony project.
</div>
Jelentkezéshez jelentkezzen be
EGYÉB POSTS Ebben a csoportban

This is the second part of the blog post showcasing the main DX (developer experience) features introduced in Symfony 7.3. Read the first part of this blog post.
Verify URI Signatures… https://symfon

Symfony 6.4.22 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in you

Symfony 7.2.7 has just been released. Read the Symfony upgrade guide to learn more about upgrading Symfony and use the SymfonyInsight upgrade reports to detect the code you will need to change in your

Symfony 7.3.0 has just been released. Check the New in Symfony 7.3 posts on this blog to learn about the main features of this new stable release; or check the first beta release announcement to get t

Symfony 7.3.0 has been released. As for any other Symfony release, our backward compatibility promise applies and this means that you should be able to upgrade easily to 7.3 without changing anything

Symfony 7.3 includes many small improvements aimed at making developers' lives easier and more productive. This blog post highlights some of the most useful DX (Developer Experience) features added in

Symfony 7.3 introduces several enhancements to the Validator component, focusing on developer experience, better configurability, and more expressive constraint definitions.
Allow to Disable Translat