Strict Mode for Missing Assets
Contributed by Jérôme Tamarelle
in #38495.
In Symfony applications you can use a JSON file manifest as the strategy to manage asset versions. When a requested asset is not listed in manifest.json, Symfony returns the unmodified path of the asset. This prevents the application from breaking when some asset is missing but generates 404 errors in the browser when trying to load the asset. In Symfony 5.4 we've added a strict_mode option (which is disabled by default). When it's true, the application triggers an exception for missing assets, so you can solve the issue. That's why it's recommended to use '%kernel.debug%' as its value, so the application breaks in dev/test but keeps working in production:
1
2 3 4 5 6
config/packages/assets.yaml
framework: assets: packages: app: strict_mode: '%kernel.debug%'
Copy File Paths in Error Pages
Contributed by Lorenzo Millucci
in #40052.
The file paths of error traces in exception pages are clickable. If you configure the framework.ide option properly, you can open those files directly on PhpStorm, VS Code, SublimeText, etc. In Symfony 5.4 we've improved this page a bit more so you can copy those file paths to clipboard. You only need to move your mouse over some row and you'll see a new clipboard icon to click on it:
Allow to Exclude Directories from Yaml Linting
Contributed by Christin Gruber
in #39641.
The lint:yaml command is a nice little tool used for example to find errors in translation files. However, sometimes you might have YAML files which use a custom syntax extensions or advanced features not supported by the YAML linter. In those cases, use the new --exclude option to not lint the files included in the given directories:
1
2 3 4 $ php bin/console lint:yaml translations/ --exclude=translations/experimental/
you can exclude multiple directories
$ php bin/console lint:yaml translations/ --exclude=translations/draft/ --exclude=translations/discarded/
New Nil ULID Class
Contributed by Thomas Calvet
in #41802.
The Uid component provides utilities to work with UUIDs and ULIDs. The UUID standard defines a NilUuid object to represent null UUID values and Symfony component implements it. However, even if the ULID standard doesn't define a NilUlid object, in Symfony 5.4 we've decided to add it so you can easily create and check for null ULID values:
1
2 3 4 5 6 7 8 9
BEFORE
use Symfony\Component\Uid\Ulid;
$nilUlid = new Ulid('00000000000000000000000000');
AFTER
use Symfony\Component\Uid\NilUlid;
$nilUlid = new NilUlid();
New String Functions
Contributed by Nicolas Grekas
in #43481.
The String component provides an object-oriented API for strings and deals with bytes, UTF-8 code points and grapheme clusters in a unified way. In Symfony 5.4 we've added two new functions to it:
1
2 3 4 5 6 7 8 9 10 // removes the given content from the start/end of the string u('file-image-0001.png')->trimPrefix('file-'); // 'image-0001.png' u('file-image-0001.png')->trimPrefix('image-'); // 'file-image-0001.png'
u('template.html.twig')->trimSuffix('.html'); // 'template.html.twig' u('template.html.twig')->trimSuffix('.twig'); // 'template.html'
// when passing an array of prefix/sufix, only the first one found is trimmed u('file-image-0001.png')->trimPrefix(['file-', 'image-']); // 'image-0001.png' u('template.html.twig')->trimSuffix(['.twig', '.html']); // 'template.html'
Sponsor the Symfony project.
Login to add comment
Other posts in this group
This blog post highlights the key accomplishments of the Symfony project in 2024. We are grateful for your continuous support, which enabled the Symfony project to achieve a remarkable year.
Releases
This week, Symfony 6.4.17, 7.1.10 and 7.2.2 maintenance versions were released. In addition, we published more information about the upcoming SymfonyOnline January 2025 conference.
Symfony developmen
Get ready for the exciting SymfonyOnline January 2025, kicking off shortly on January 16-17! There’s still time to register and join the international online Symfony conference—along with pre-
Symfony 6.4.17 has just been released. Here is the list of the most important changes since 6.4.16:
bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario G
Symfony 7.1.10 has just been released. Here is the list of the most important changes since 7.1.9:
bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario Gu
Symfony 7.2.2 has just been released. Here is the list of the most important changes since 7.2.1:
bug #59304 [PropertyInfo] Remove @internal from PropertyReadInfo and PropertyWriteInfo (Dario Gua
This week, we launched the new Twig playground, a tool that lets you test and experiment with Twig features in a safe, sandboxed environment. While Symfony development activity was lighter than usual