SymfonyWorld Online 2021 Winter Edition December 9 – 10, 2021 100% Online +20 talks and workshops

A week of symfony #511 (10-16 October 2016)

This week Symfony continued fixing some minor bugs and integrating the last new features after the recent "feature freeze" for the upcoming 3.2 version. A new option was added to select the repository used by the UniqueEntity validator and the HttpCache was fixed to not cache requests with the OPTIONS HTTP method. Lastly, the new SecurityUserValueResolver and the controller getUser() method was undeprecated.

Symfony development highlights

2.7 changelog:

  • 705a4f7: [Validator] prevent infinite loop in PropertyMetadata
  • 55c3f89: [HttpCache] do not cache requests that use the OPTIONS HTTP method
  • 7e2f24f: [DependencyInjection] moved tags from decorated to decorating service
  • 8d218e7: [HttpFoundation] no 304 response if method is not cacheable
  • 287713f: [Filesystem] fixed Filesystem:makePathRelative and added 2 more testcases

2.8 changelog:

  • adf20c8: updated the Upgrade Guide to explain how to pass data to a form through options resolver

Master changelog:

  • 406462f, 115a379: [DependencyInjection] fixed duplication of environment variables placeholders
  • 4cc2424: [TwigBridge] updated the upgrade instructions
  • bf2ff76: [SecurityBundle] cache contexts per request in FirewallMap
  • 0f76683: changed mentions of 'symfony2' to 'symfony'
  • 69e8654: [DoctrineBridge] added a way to select the repository used by the UniqueEntity validator
  • f9bb4ab: [FrameworkBundle] removed the new SecurityUserValueResolver

Newest issues and pull requests

Twig development highlights

Master changelog:

  • 3879038: improved Sandbox error handling
  • ef942f6: made it possible to store templates with vfsStream

They talked about us

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.


The commit message being misleading, I think it's important to mention that in fact the SecurityUserValueResolver has not been removed, we just reverted the deprecation of the getUser method so both ways stay good to use.

Comments are closed.

To ensure that comments stay relevant, they are closed for old posts.