We've had one feature for couple of months now,
but only now we're adding it to compser based sets.
It will be blast!
Rector rule bound to exact package and version the feature was released 😎
Zero work for you, flawless upgrade by Rector
Rector
@rectorphp
Instant Upgrades and Instant Refactorings for PHP Applications. Why do it manually?
#rectorphp
Created by @votrubaT
- Just add ->withPhpSets() to your rector.php, and enjoy all the new PHP features 👍PHP tip. Since PHP 8.2 you can mark the whole class `readonly` instead of repeating the keyword on every property. Every property becomes readonly automatically, and anything you add later is covered too. No way to forget one.
- Upgrading @rectorphp's codebase has its benefits (that any project can use) * bump PHPUnit 12 → 13 * CI fails because PHPStan spots deprecated methods in PHPUnit * Rector spots new dependency in composer.json * Rector looks for PHPUnit 13 upgrade rules * applies them and
- The @pestphp introduces Plugin Rector, so your tests are always in the best shape! Live at Laracon US
- Interested in such an upgrade? Hire us: getrector.com/hire-teamI'm slowly noticing how GPT helps to increase quality of my upgrade service. Before, when client wanted to catch this detail or that detail, that is not part of typical ECS, Rector or PHPStan sets, I struggled with convincing myself to write a new rule to handle it. To be
