This week Symfony released 2.7.16, 2.8.9, 3.0.9 and 3.1.3 maintenance versions. Meanwhile, HttpCache lock files were improved by using flock(), a new cache warmer for annotations was enabled and the "add classes to compile" feature was improved to support patterns and annotated classes.
In this article, we're thrilled to introduce the new Symfony Documentation: a result of over 150 hours of volunteer work to reword most contents and reorganize the entire documentation.
This week Symfony added forward compatibility with the upcoming PHP 7.1 version, which will trigger notices on previously silent implicit type changes. The master version also added an option to the translation:update command to filter by the translation domain. Lastly, the SymfonyLive London 2016 schedule was revealed and the SymfonyCon Berlin 2016 schedule was partially unveiled.
In Symfony 3.2 we added a new Workflow component to help you define "workflows", which are elements that describe a sequence of operations that can be executed repeatedly to provide some service (e.g. buying a product in an e-commerce application), process some information (e.g. publishing some content in a CMS application), etc.
This week, Symfony's activity slowed down significantly, as it always happens during the mid-summer on the Northern Hemisphere: a bug related to the retrieval of the username when using forwarding was fixed, the list of HTTP safe methods was updated and Serializer added support for argument objects.
Symfony 3.2 added support for "same-site" cookie attribute, fixed some inconsistencies in cache-related HTTP headers and added a new method called isMethodIdempotent().
In Symfony 3.2, we've added a new user resolver that allows to get the current user in any controller via type-hinting and we deprecated the Controller::getUser() shortcut, which will be removed in Symfony 4.0.
ChoiceType is the most powerful Symfony form type and it's used to create select drop-downs, radio buttons and checkboxes. In Symfony 3.2 we added a new feature to improve its performance: lazy loading the choice values.
In Symfony 3.2, YAML files added support for including underscores in numeric literals (integer, float or hexadecimal) to improve their readability.
This week Symfony focused on fixing issues and tweaking existing features. Meanwhile, we continued blogging about the new Symfony 3.2 features. Lastly, the SymfonyLive Chicago Call for Papers was announced while the Call for Papers for SymfonyLive London and SymfonyCon Berlin will finish next week.
In this second of a three-part series, we introduce four additional new features added by Symfony 3.2 to the Console component to improve its DX (developer experience).
The Console component will receive a lot of new features in Symfony 3.2, mostly related to improving its DX (developer experience). In this first of a three-part series, we introduce four of those new features.
Symfony 3.2 adds support to define the fragment when generating any URL. It also adds support for using arrays and defining the variable types for XML route values.
Symfony 3.2 improves the cache mechanism introduced in Symfony 3.1 with some features not defined by the PSR-6: Caching Interface standard. The first new feature is the tag-based invalidation to create tagged caches.
Symfony 3.2 includes a new DateInterval form type to deal with calendar-related information such as reminders and bookings.
This week, Symfony 2.7.15, 2.8.8, 3.0.8 and 3.1.2 maintenance versions were released. Meanwhile, the upcoming Symfony 3.2 version continued adding new features, such as support for setter injection autowiring, configurable output for VarDumper component, deprecated access to private services and a new security resolver to get the current user via controller typehints.
Compiler passes are the mechanism provided by Symfony to manipulate the service definitions while the container is being compiled before the application execution. In Symfony 3.2 we introduced some new features for them.