Black Friday 2021 Offers 30% discount on Certification, Coaching, and SymfonyInsight Teams subscriptions

A Week of Symfony #719 (5-11 October 2020)

This week of Symfony blog post is backed by SensioLabs. As the creator of Symfony, SensioLabs supports companies using Symfony, with an offering encompassing consultancy, expertise, services, training, and technical assistance to ensure the success of web application development projects.

This week Symfony 4.4.15 and 5.1.7 maintenance versions were released. Meanwhile, development activity focused on fixing and polishing the upcoming Symfony 5.2 features and Symfony 5.2 beta1 was published. Finally, Symfony Insight announced a free webinar on software quality.

Symfony development highlights

This week, 84 pull requests were merged (46 in code and 38 in docs) and 78 issues were closed (49 in code and 29 in docs). Excluding merges, 42 authors made 5,942 additions and 4,755 deletions. See details for code and docs.

3.4 changelog:

  • c4aeb6f: [VarDumper] fixed truncating big arrays
  • 27c2260: [PhpUnitBridge] fixed running parallel tests with PHPUnit 9
  • 7173d6c: [PropertyInfo] support for the mixed type
  • 9ffad84: [Validator] updated Brazilian Portuguese translation
  • 4beb659: [Validator] updated Serbian translation
  • b95ad41: [Validator] updated Bosnian translation

4.4 changelog:

  • 87f3284: [Mime] fixed serialization of RawMessage
  • 45cad64: [Ldap] bypass the use of ldap_control_paged_result on PHP >= 7.3
  • 1cef665: [HttpClient] fixed CurlHttpClient memory leak

5.1 changelog:

  • 392f2e0: [PropertyInfo] fixed extraction from default value doesn't set collection boolean

5.x changelog:

  • a4ceab6: [Cache] allow ISO 8601 time intervals to specify default lifetime
  • a324b22, 5a3e1db: [HttpClient] minor fixes in RetryableHttpClient
  • 2f925df: [Validator] migrate File and Image constraints to attributes
  • c4141f5: [DoctrineBridge] fixed and replaced namespace to Uid
  • 81833b6: [FrameworkBundle] added option --as-tree to translation:update command
  • 1428e6d: [SecurityGuard] implemented PostAuthenticationGuardToken::getFirewallName()
  • b0ae228: [Translation] renamed Translatable class to TranslatableMessage
  • 5cc4bc9: [Lock] added store dedicated to PostgreSQL
  • 494ef42: [HttpClient] added jitter to RetryBackoff
  • 4c34426: [Form] fixed field_value Twig helper for multiple choices
  • 61dcfe3: [SecurityBundle] made user lazy loading working without user provider
  • 414a5ab: [Lock] mark Key unserializable whith PgsqlStore
  • 559ebe3: [PhpUnitBridge] added ability to set a baseline for deprecation testing
  • 0137609: [Notifier] introduced NullMessage and remove transport setter in MessageInterface
  • 0000dfe: [Messenger] added DelayStamp::delayFor() and DelayStamp::delayUntil()
  • d1f2faf: [RateLimiter] fixed framework configuration
  • 3ec2c8a: [Security] added error message when using LoginLinkHandler outside a firewall
  • b9d4a2b: [Security] allowed null and DateTime objects to be used as Login Link signatureProperties
  • 87920d2: [Validator] upgraded constraints to enable named arguments and attributes

Symfony CLI

Symfony CLI is a must-have tool when developing Symfony applications on your local machine. It includes the Symfony Local Server, the best way to run local Symfony applications. This week Symfony CLI released its new 4.19.1 and 4.19.2 versions with the following changes:

  • Add a --host flag to local:proxy:start to define the host exposed in the generated PAC file
  • Improve local:server:start start performance
  • Improve local:proxy:start start performance
  • Fix phpbrew support for the local web server when using versions aliases
  • Fix preloading issues preventing code changes to be taken into account at deployment
  • Improve hints about deploying to the main environment for the first time
  • Make it easier to run one-liner scripts using symfony ssh
  • Fix panic in symfony ssh when providing a command to execute

Newest issues and pull requests

They talked about us

Call to Action

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.