Typo3 Rector Laravel Package

Product Decisions This Supports

• TYPO3 Version Upgrades: Automate migration from older TYPO3 versions (v10–v14) to newer ones, reducing manual effort and risk of breaking changes. Aligns with roadmap goals for backward compatibility and modernization.
• Build vs. Buy: Buy—this is a specialized, maintained tool for TYPO3-specific refactoring, avoiding reinventing the wheel for PHP/TS/FlexForm migrations.
• Developer Productivity: Reduce time spent on deprecation warnings and manual code adjustments by automating 80% of migration tasks (e.g., Fluid templates, TCA, Extbase).
• Extension Maintenance: Critical for third-party extension developers targeting TYPO3 v14+ (e.g., migrating makeCategorizable() or fluid classnames to standalone syntax).
• CI/CD Integration: Enable pre-commit hooks or GitHub Actions to auto-fix deprecated code, improving code quality gates.
• Security Compliance: Automate updates to stronger cryptographic algorithms (e.g., UseStrongerCryptographicAlgorithmForHMACRector) or remove outdated version checks.

When to Consider This Package

• Avoid if:
  • Your project uses TYPO3 <v10 or >v14 (limited rule support).
  • You need non-PHP file migrations (e.g., TypoScript, FlexForm, YAML) → Use fractor instead.
  • Your team lacks coding standards tools (e.g., ECS) to format Rector’s output.
  • You’re not upgrading TYPO3—this is a migration tool, not a general refactoring library.
• Consider if:
  • You’re migrating TYPO3 v10–v14 and want to minimize manual work.
  • Your codebase has deprecation warnings (e.g., TYPO3\CMS\Core\Utility\GeneralUtility::makeInstance()).
  • You need to future-proof extensions for TYPO3’s evolving APIs (e.g., Fluid, TCA, Extbase).
  • Your team prioritizes automated, safe refactoring over manual edits.

How to Pitch It (Stakeholders)

For Executives: "TYPO3 Rector automates 80% of the tedious, error-prone work in upgrading from TYPO3 v10–v14, saving dev teams weeks of manual labor while reducing risks of breaking changes. It’s like GitHub Copilot for migrations—just run a CLI command to modernize your codebase safely. For a one-time setup cost (dev environment + ECS), we gain faster upgrades, fewer bugs, and compliance with TYPO3’s latest security standards (e.g., cryptographic updates). Competitors like fractor don’t cover PHP refactoring, making this a unique, high-leverage tool for our roadmap."

For Engineering: *"This is a force multiplier for TYPO3 upgrades. It handles:

• Deprecation hell: Auto-fixes GeneralUtility::makeInstance(), Fluid template changes, and TCA migrations.
• CI/CD safety: Dry-run mode lets us test changes before merging (vendor/bin/rector process --dry-run).
• Extension compatibility: Rules like RemoveTypo3VersionChecksRector ensure our extensions work across TYPO3 versions. Downside: Requires ECS for formatting, but the tradeoff is worth it for zero manual refactoring. Let’s pilot it on [Project X]’s v11→v14 upgrade—if it saves 10 dev-days, it pays for itself."*