Living on the Edge
A series of posts showcasing the new features introduced by each Symfony version.
In Symfony 4.1, working with Single-Page Applications will be easier thanks to the self-updating debug toolbar
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.
In Symfony 4.1 sessions can be migrated to new storage handlers and some requests that use sessions can now be cached.
Symfony 4.1 introduces new exception classes and improves the exception pages design to be more actionable and display more accurate information.
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.
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.
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.
In Symfony 4.1 you can ignore the log messages related to specific HTTP status codes so your log files are not polluted with irrelevant messages.
In Symfony 4.1, the output of console commands goes to the next level with multiple editable sections, overwritable contents and dynamic tables.
Symfony 4.1 adds a new Messenger component that helps applications send and receive messages to/from other applications or via message queues. It provides a message bus based on middlewares, some routing capabilities and built-in support for AMQP brokers.