6.7 KiB
Rector Reconstructs your Legacy Code to Modern Codebase
Rector upgrades your application for you, with focus on open-source projects:
Install
composer require --dev rector/rector @dev nikic/php-parser 'dev-master#5900d78 as v3.1.1'
Do you have old PHP or dependencies in conflict? Ok, it is not problem.
How To Reconstruct your Code?
A. Prepared Sets
Fetaured open-source projects have prepared sets. You'll find them in /src/config/level
.
E.g. Do you need to upgrade to Symfony 3.3?
- Run rector on your
/src
directory
vendor/bin/rector process src --level symfony33
Which is just a shortcut for using complete path with --config
option:
vendor/bin/rector process src --config vendor/rector/rector/src/config/level/symfony/symfony33.yml
You can also use your own config file:
vendor/bin/rector process src --config your-own-config.yml
- Check the Git
git diff
B. Custom Sets
- Create
rector.yml
with desired Rectors
rectors:
- Rector\Rector\Contrib\Nette\Application\InjectPropertyRector
- Run rector on your
/src
directory
vendor/bin/rector process src
- Check the Git
git diff
Simple setup with Dynamic Rectors
You don't have to always write PHP code. Many projects change only classes or method names, so it would be too much work for a simple task.
Instead you can use prepared Dynamic Rectors directly in *.yml
config:
You can:
-
replace class name
# phpunit60.yml rectors: Rector\Rector\Dynamic\ClassReplacerRector: # old class: new class 'PHPUnit_Framework_TestCase': 'PHPUnit\Framework\TestCase'
-
replace part of namespace
# better-reflection20.yml rectors: Rector\Rector\Dynamic\NamespaceReplacerRector: # old namespace: new namespace 'BetterReflection': 'Roave\BetterReflection'
-
change method name
rectors: Rector\Rector\Dynamic\MethodNameReplacerRector: # class 'Nette\Utils\Html': # old method: new method 'add': 'addHtml' # or in case of static methods calls # class 'Nette\Bridges\FormsLatte\FormMacros': # old method: [new class, new method] 'renderFormBegin': ['Nette\Bridges\FormsLatte\Runtime', 'renderFormBegin']
-
change property name
rectors: Rector\Rector\Dynamic\PropertyNameReplacerRector: # class: # old property: new property 'PhpParser\Node\Param': 'name': 'var'
-
change class constant name
rectors: Rector\Rector\Dynamic\ClassConstantReplacerRector: # class 'Symfony\Component\Form\FormEvents': # old constant: new constant 'PRE_BIND': 'PRE_SUBMIT' 'BIND': 'SUBMIT' 'POST_BIND': 'POST_SUBMIT'
-
change parameters typehint according to parent type
rectors: Rector\Rector\Dynamic\ParentTypehintedArgumentRector: # class 'PhpParser\Parser': # method 'parse': # parameter: typehint 'code': 'string'
-
change argument value
rectors: Rector\Rector\Dynamic\ArgumentReplacerRector: # class 'Symfony\Component\DependencyInjection\ContainerBuilder': # method 'compile': # argument position 0: # added default value ~: false # or remove completely ~: ~ # or replace by new value 'Symfony\Component\DependencyInjection\ContainerBuilder\ContainerBuilder::SCOPE_PROTOTYPE': false
-
or replace underscore naming
_
with namespaces\
rectors: Rector\Roector\Dynamic\PseudoNamespaceToNamespaceRector: # old namespace prefix - 'PHPUnit_' # exclude classes - '!PHPUnit_Framework_MockObject_MockObject'
6 Steps to Add New Rector
In case you need a transformation that you didn't find in Dynamic Rectors, you can create your own:
- Just extend
Rector\Rector\AbstractRector
class. It will prepare 2 methods:
public function isCandidate(Node $node): bool
{
}
public function refactor(Node $node): ?Node
{
}
- Put it under
namespace Rector\Contrib\<set>;
namespace
<?php declare(strict_types=1);
namespace Rector\Contrib\Symfony;
use Rector\Rector\AbstractRector;
final class MyRector extends AbstractRector
{
// ...
}
-
Add a Test Case
-
Add to specific level, e.g.
/src/config/level/symfony/symfony33.yml
-
Submit PR
-
👍
Coding Standards are Outsourced
This package has no intention in formatting your code, as coding standard tools handle this much better.
We prefer EasyCodingStandard that is already available (no install needed):
# check
vendor/bin/ecs check --config vendor/rector/rector/ecs-after-rector.neon
# fix
vendor/bin/ecs check --config vendor/rector/rector/ecs-after-rector.neon --fix
but you can use any other with this setup.
Advanced Operations
How to Contribute
Just follow 3 rules:
-
1 feature per pull-request
-
New feature needs tests
-
Tests, coding standard and PHPStan checks must pass
composer all
Don you need to fix coding standards? Run:
composer fix-cs
We would be happy to merge your feature then.