Symfony Blog
New in Symfony 4.1: Self-updating debug toolbar
In Symfony 4.1, working with Single-Page Applications will be easier thanks to the self-updating debug toolbar
A week of symfony #591 (23-29 April 2018)
This week, development activity was focused on improving the new Messenger component to allow defining multiple buses, adding a memory limit option to ConsumeMessagesCommand and generating better logs for received messages. In addition, we improved the performance of the resource loading in the Translator component and the performance of the normalizer in the Serializer component.
New in Symfony 4.1: Session improvements
In Symfony 4.1 sessions can be migrated to new storage handlers and some requests that use sessions can now be cached.
New in Symfony 4.1: Exception improvements
Symfony 4.1 introduces new exception classes and improves the exception pages design to be more actionable and display more accurate information.
New in Symfony 4.1: HTTP header improvements
Symfony 4.1 introduces a new utility class to work with HTTP headers, adds support for default values in Accept headers and it allows to bypass HTTP headers when submitting forms in tests.
A week of symfony #590 (16-22 April 2018)
This week, Symfony improved the performance of the Cache component inlining some function calls and simplified the usage of the new Messenger component allowing to omit the sender tag name and to use the adapter name instead of the service name. In addition, we added a new dd() helper which is useful when you can't or don't want to use a debugger.
New in Symfony 4.1: Serializer improvements
In Symfony 4.1 the serializer can normalize validation errors automatically, it can define default constructor arguments when denormalizing contents, it allows to use custom max depth handlers and it ignores XML comments by default.
New in Symfony 4.1: Ajax improvements
In Symfony 4.1 it's easier to make Ajax requests in functional tests and the Ajax panel in the debug toolbar has been improved.