Typo3 Rector

What it does

This skill, Typo3 Rector, uses the Rector automated refactoring tool to update TYPO3 PHP codebases between major versions. It applies predefined rules to address deprecated code patterns and ensure compatibility with TYPO3 v14. It's designed to catch namespace changes, method signature updates, and other common issues that are difficult to identify manually. Note: for non-PHP migrations (FlexForms, TypoScript, Fluid, YAML), use the typo3-fractor skill instead.

When to use it

• When upgrading a TYPO3 project to version 14.
• To automatically correct common code patterns that are deprecated in newer versions of TYPO3.
• As part of regular maintenance to ensure code consistency and prevent future compatibility issues.
• Before deploying changes to a production environment running TYPO3 v14.

Key capabilities

• Automated refactoring of TYPO3 PHP code.
• Compatibility with TYPO3 version 14 (v14.x).
• Detection and correction of deprecated code patterns.
• Handles TYPO3 namespace changes and method signature updates.
• Requires PHP 8.2 or higher to run, or the use of a container like DDEV.

Example prompts

• "Run Typo3 Rector on my project."
• "Perform a dry-run of Typo3 Rector to see what changes it would make."
• "Update my TYPO3 code to be compatible with version 14 using Typo3 Rector."

Tips & gotchas

• PHP Version Requirement: Typo3 Rector requires PHP 8.2 or higher due to the use of readonly classes and other syntax in TYPO3 v14 packages. Use DDEV or a container if your local PHP version is older.
• Always Run: It's crucial to run Typo3 Rector; manual replacements often miss edge cases that Rector rules handle correctly.
• Configuration: A rector.php file needs to be created in the project root for basic configuration, specifying paths and skips.