padina42/typo3-rector

Rector for TYPO3

❗ Caution: Never run this tool on production, only on development environment where code is under version control (e.g. git). Always review and test automatic changes before releasing to production.

Rector for TYPO3

This project lets you apply instant upgrades and instant refactoring to your TYPO3 Core and extension code, making it easier to migrate between TYPO3 releases and keeping your code free from deprecation.

It extends the Rector project, which aims to provide instant upgrades and instant refactoring for any PHP code (5.3+).

	URL
Repository:	https://github.com/sabbelasichon/typo3-rector
Documentation:	https://github.com/sabbelasichon/typo3-rector/tree/main/docs
Packagist:	https://packagist.org/packages/ssch/typo3-rector
Website:	https://www.typo3-rector.com

Funding/Sponsoring

Help us out and sponsor our work! Visit our website typo3-rector.com for more info.

This makes it possible to invest more time to keep the project alive and create even more rules for automated migration.

Support

Please post questions in the TYPO3 Slack channel #ext-typo3-rector or feel free to open an issue or start a discussion on GitHub.

Credits

Many thanks to Tomas Votruba for his ongoing support and Rector. Many thanks to every other contributor.

Follow us on twitter as well:

• TYPO3 Rector
• Sebastian
• Henrik

Known Drawbacks

How to Apply Coding Standards?

Rector uses nikic/php-parser, built on technology called an abstract syntax tree (AST). An AST doesn't know about spaces and when written to a file it produces poorly formatted code in both PHP and docblock annotations. That's why your project needs to have a coding standard tool and a set of formatting rules, so it can make Rector's output code nice and shiny again.

We're using ECS with this setup.