Automate Drupal 9 upgrades: Addressing deprecated code as a community
summary
Automation aims to replace repetitive deprecations so Drupal 8 sites run on Drupal 9 faster by using Rector plus a Drupal-specific config called Drupal Rector; it already auto-rewrites common cases like Drupal_set_message (dry-run shows git-style diffs) and has partial rules for entityManager and PHPUnit getMock, while heavier fixes currently emit dependency injection TODOs. Setup uses PHPStan/Drupal Check, example modules, Xdebug and IDE hints; test coverage and full DI conversions are still incomplete but the project is active and open for contribution.
AI-written summary · about
chapters (24)
- 0:00Intro
- 0:45Dan Montgomery
- 4:52Acquia Online Deprecation Status Tool: Example
- 5:29Drupal Check local development tool
- 8:32In-code notice: PhpStorm
- 8:59Core code comments
- 9:38Manual update
- 12:07Drupal Rector (more details)
- 14:56Manual testing
- 15:18Process review: Updating code
- 16:18Supported deprecations
- 19:42Create an example of deprecated usage
- 20:01Create a class
- 20:32Register the class
- 22:12Method: getDefinition
- 23:00Method: getNode Types
- 24:09Method: refactor
- 27:18Documentation and references
- 28:08Drupal Rector Introduction
- 29:18Drupal Rector development sandbox
- 31:11Palantir.net goals
- 32:20Community goals & opportunities
- 33:38Original Drupal 8 Rector project
- 34:14Drupal Rector maintainer
related talks
47mUpgrading to Drupal 10: A real case
01h 04mBye bye drupalisms! Propelling Drupal into a modern PHP ecosystem
22mInstant Upgrades with Rector
14mInstant Upgrades with Rector
49mElevating Legacy: A Case Study on the migration from Laravel 4 to 9
29mTomas Votruba — Let Rector do the Boring Work
50mPHP 8.2 - Just upgrade and go?
41mWhat’s New in Drupal 8?