New in Symfony 6.1: Improved Routing Requirements and UTF-8 Parameters
April 25, 2022 • Published by Javier Eguiluz
Symfony 6.1 is backed by:
Warning: This post is about an unsupported Symfony version. Some of this information may be out of date. Read the most recent Symfony Docs.
Using PHP BackedEnum as Route Requirements
In PHP, backed enumerations are enumerations where all its elements are backed by some scalar value. This makes them useful to restrict the possible values of some routing parameter. In previous Symfony versions, you had to create the requirements manually using public constants:
1
#[Route('/foo/{bar}', requirements: ['bar' => SomeEnum::AAA.'|'.SomeEnum::BBB])]
In Symfony 6.1, we're improving the Routing component to fully support
\BackedEnum
objects as follows:
1 2 3 4 5 6 7
use Symfony\Component\Routing\Requirement\EnumRequirement;
// 'bar' parameter allows all values defined in the Enum
#[Route('/foo/{bar}', requirements: ['bar' => new EnumRequirement(SomeEnum::class)])]
// 'bar' parameter only allows certain values of those defined in the Enum
#[Route('/foo/{bar}', requirements: ['bar' => new EnumRequirement([SomeEnum::class, SomeEnum::Aaa, SomeEnum::Bbb])])]
A Collection of Common Routing Requirements
When defining routes, there are some requirements that repeat on many projects.
For example, restricting some value to be an integer, or a date or a valid UUID
pattern. In Symfony 6.1 we're introducing a Requirement
enumeration to
define all those common routing requirements so you can use them in your projects:
1 2 3 4 5 6 7 8 9 10 11 12
use Symfony\Component\Routing\Requirement\Requirement;
#[Route('/users/{id}', requirements: ['id' => Requirement::UUID_V4])]
#[Route('/users/{id<'.Requirement::UID_BASE58.'>}')]
#[Route('/posts/{date}/{slug}', requirements: [
'date' => Requirement::DATE_YMD,
'slug' => Requirement::ASCII_SLUG,
])]
// 'CATCH_ALL' is equivalent to '.+' (accepts all characters, including '/')
#[Route('/category/{name}', requirements: ['name' => Requirement::CATCH_ALL])]
UTF-8 Parameter Names
In PHP, variable identifiers can contain UTF-8 characters (e.g. $iñtërnâtiónàlizætiøn = '...'
)
However, parameters in Symfony routes could only include ASCII characters.
In Symfony 6.1 we're improving the Routing component to allow using UTF-8
characters in all route parameters:
1 2 3 4 5 6 7
use Symfony\Component\Routing\Annotation\Route;
#[Route('/blog/{föo}/{bár}', name: '...')]
public function someControllerMethod(string $föo, string $bár)
{
// ...
}
Help the Symfony project!
As with any Open-Source project, contributing code or documentation is the most common way to help, but we also have a wide range of sponsoring opportunities.
Comments are closed.
To ensure that comments stay relevant, they are closed for old posts.
```
use Symfony\Component\Routing\Requirement\EnumRequirement;
// 'bar' parameter allows all values defined in the Enum
#[Route('/foo/{bar}', requirements: ['bar' => new EnumRequirement(SomeEnum::class)])]
// 'bar' parameter only allows certain values of an Enum
#[Route('/foo/{bar}', requirements: ['bar' => new EnumRequirement([SomeEnum::Aaa, SomeEnum::Bbb])])]
```
A collection of common requirements now makes the code more consistent.