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

A Week of Symfony #676 (9-15 December 2019)

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, the upcoming Symfony 5.1 version added MongoDB support for the Lock component, exception pages enabled the "dark theme" and the MicroKernelTrait was improved to make it easier to use and configure.

Symfony development highlights

This week, 74 pull requests were merged (38 in code and 36 in docs) and 54 issues were closed (34 in code and 20 in docs). Excluding merges, 31 authors made 1,421 additions and 752 deletions. See details for code and docs.

3.4 changelog:

  • bf877b8: [TwigBundle] add tags before processing them
  • 56bfbd8: [PropertyAccess] forward caught exception
  • 429b18e: [Validator] stop passing unnecessary timezone argument to \DateTime in ConstraintValidator
  • 2eacbc5: [ExpressionLanguage] process division by zero
  • 8aefe97: [MonologBridge] fix debug processor datetime type
  • 035d8a3: [Yaml] implement multiline string as scalar block for tagged values
  • 42712ee: [HttpFoundation] use Cache-Control: must-revalidate only if explicit lifetime has been given
  • 349ea04: [Translation] fixed memoryleak in PhpFileLoader
  • cff8b25: [DoctrineBridge] try to fix deprecations from doctrine/persistence
  • e043316: [Validator] safe fail on invalid timezones in ConstraintValidator

4.3 changelog:

  • 3df1d1e: [Cache] propagate expiry when syncing items in ChainAdapter
  • ebadf51: [Routing] fixed memory leak when loading compiled routes
  • d294085: [DependencyInjection] fixed support for immutable setters in CallTrait

4.4 changelog:

  • b81f428: [FrameworkBundle] reinitialize bundles when the container is reprepared in ContainerLintCommand
  • 2e70324: [Process] changed the syntax of portable command lines
  • 7049b94: [Validator] fixed auto-mapping constraints should not be validated
  • ff1d77e: [TwigBundle] fixed findTemplate() to return null
  • d91efd3: [HttpFoundation] removed Content-Type from the preferred format guessing mechanism
  • 6bf764a: [HttpKernel] fixed triggering deprecation in file locator
  • 212dc53: [HttpFoundation] fixed Redis multi host DSN not recognized
  • 1d59e1e: [FrameworkBundle] hook local dotenv file configured for secrets
  • da7deda: [FrameworkBundle] skip removed ids in the lint container command and its associated pass

Master changelog:

  • e8ecfe3: [Lock] added mongodb store
  • 1827908: [ErrorHandler] enabled the dark theme for exception pages
  • a6d1567: [DependencyInjection] added support for defining method calls in InlineServiceConfigurator
  • 4445812: [FrameworkBundle] added flex-compatible default implementations for MicroKernelTrait::registerBundles() and getProjectDir()
  • 8c80c5b: [FrameworkBundle] allow using a ContainerConfigurator in MicroKernelTrait::configureContainer()

Symfony Local Server

Symfony Local Server, the best way to run Symfony applications on your local machine, released its new 4.11.3 version with the following changes:

  • Fix loading the local php.ini on FPM (loading PHP extensions now works)
  • Fix loading PHP config from for web servers using PHP CGI or PHP CLI
  • Remove php:wrappers:install and supports for the PHP wrappers (use symfony php/pecl/... instead)
  • Update extension list for PHP 7.4
  • Fix infinite login loop when used in non interactive environment
  • Add Blackfire integration when using Docker for the Blackfire agent
  • Fix open:remote:rabbitmq does not found the RabbitMQ management UI
  • Specify which environment will be snapshoted when running env:sync
  • Fix double spinner issue on env:sync

Newest issues and pull requests

They talked about us

Upcoming Symfony Events

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.