Symfony 7: Is Your Upgrade Ready?
summary
Symfony 7 ships as a cleanup release (the beta1 out now) that removes the deprecation layer so production code must stop using deprecated APIs; the practical claim is “Symfony 7 = Symfony 6.4 minus deprecations” (Symfony 7 = 6.4 minus deprecations). New attribute-driven features already live in 6.4: routing, DI decoration and autowiring, request payload mapping, access‑token auth, HTML sanitizer, clock, asset mapper, webhook/scheduler built on Messenger. Migration strategy uses Rector to rewrite Doctrine annotations to attributes and PHPStan’s deprecation rules to find remaining issues (use Rector + PHPStan).
AI-written summary · about
chapters (18)
- 0:00Symfony 7 introduction
- 1:25What is Symfony
- 3:11Symfony 6.4/7.0 releases
- 5:20PHP 8 attributes vs annotations
- 8:58Dependency injection improvements
- 17:50HTTP kernel enhancements
- 21:50Query parameter handling
- 25:28Exception and security attributes
- 27:35Doctrine annotations deprecated
- 29:22FrameworkExtraBundle removed
- 30:47Access token auth
- 36:05New Symfony 6.x components
- 42:12PSR HTTP message bridge
- 44:22Messenger and webhooks
- 46:29Scheduler and asset mapper
- 52:40Templating component deprecated
- 54:48Upgrade preparation
- 59:47Summary and contributions
related talks
48mDeveloping Symfony applications in 2023
52mSymfony 5, the new bits
01h 04mBye bye drupalisms! Propelling Drupal into a modern PHP ecosystem
40mSymfony deprecations: from anxiety to opportunity
43mSymfony 5
34mSymfony 4: A new Way to develop Applications
43mGetting the Most Out of the PHP 7 Engine - The Symfony Example
31mPreparing custom and contributed code for Drupal 9.