Rector is a reconstructor tool - it does instant upgrades and instant refactoring of your code. Why refactor manually if Rector can handle 80% of the task for you?

• Online DEMO
• Overview 500+ Rector Rules

Rector grows faster with your help, the more you help the more work it saves you. Check out Rector's Patreon. One-time donations are welcome through PayPal.

Thank you:

Rector instantly upgrades and instantly refactors the PHP code of your application.

It supports all versions of PHP from 5.2 and many open-source projects:

• Rename classes, methods, properties, namespaces or constants
• Complete parameter, var or return type declarations based on static analysis of your code
• Upgrade your code from PHP 5.3 to PHP 7.4
• Migrate your project from Nette to Symfony
• Complete PHP 7.4 property type declarations
• Refactor Laravel facades to dependency injection
• And much more...

Rector uses nikic/php-parser, that build on technology called abstract syntax tree) technology* (AST). AST doesn't care about spaces and produces mall-formatted code. That's why your project needs to have coding standard tool and set of rules, so it can make refactored nice and shiny again.

Don't have any coding standard tool? Add EasyCodingStandard and use prepared ecs-after-rector.yaml set.

• Having conflicts during composer require? - Use the Rector Prefixed
• Using a different PHP version than Rector supports? - Use the Docker image

Featured open-source projects have prepared sets. You can find them in /config/set or by running:

Let's say you pick the symfony40 set and you want to upgrade your /src directory:

Rector will show you diff of files that it would change. To make the changes, run same command without --dry-run:

Some sets, such as code-quality can be used on a regular basis. The best practise is to use config over CLI, here in sets parameter:

In the end, it's best to combine few of basic sets and drop particular rules that you want to try:

Then let Rector refactor your code:

Note: rector.yaml is loaded by default. For different location, use --config option.

If you're annoyed by repeating paths in arguments, you can move them to config instead:

Rector relies on whatever autoload setup the project it is fixing is using by using the Composer autoloader as default. To specify your own autoload file, use --autoload-file option:

Or use a rector.yaml configuration file:

You can also exclude files or directories (with regex or fnmatch):

You can use a whole set, except 1 rule:

For in-file exclusion, use @noRector \FQN name annotation:

By default Rector uses the language features matching your system version of PHP. You can configure it for a different PHP version:

FQN classes are not imported by default. If you don't want to do it manually after every Rector run, enable it by:

You can also fine-tune how these imports are processed:

Execution can be limited to changed files using the process option --match-git-diff. This option will filter the files included by the configuration, creating an intersection with the files listed in git diff.

This option is useful in CI with pull-requests that only change few files.

To work with some Symfony rules, you now need to link your container XML file

• All Rectors Overview
• Create own Rule
• Generate Rector from Recipe
• How Does Rector Work?
• PHP Parser Nodes Overview
• Add Checkstyle with your CI

See the contribution guide.

You can run Rector on your project using Docker:

Using rector.yaml:

Do you use Rector to upgrade your code? Add it here:

• palantirnet/drupal-rector by Palantir.net for Drupal
• sabbelasichon/typo3-rector for TYPO3