Rector @rectorphp

Instant Upgrades and Instant Refactorings for PHP Applications. Why do it manually? #rectorphp Created by @votrubaT getrector.com/hire-team PHP Community Joined December 2018

Tweets

3K
Followers

4K
Following

2
Likes

3K

Rector @rectorphp

9 hours ago

What is new in Rector 2.5? Rector will report you skips that are no longer needed (opt-in for early testing) ⬇️

0 1 2 382 0

View Details

Tomas Votruba @VotrubaT

23 hours ago

It's the little details that matters. Coming to @rectorphp code quality set

2 3 19 1K 3

View Details

Rector 2.5 came with unused skips feature to cleanup your configs. Run Rector on the whole project, without cache, to get the results: vendor/bin/rector --clear-cache --dry-run But how does it look like on a real project? Here in Mautic we removed 45 lines from rector.php ⬇️ github.com/mautic/mautic/… Much readable 😊

0 2 7 799 1

View Details

Rector @rectorphp

3 days ago

🧹 @rectorphp 2.5 is out! New: ->reportUnusedSkips() - like PHPStan's reportUnusedIgnores, but for your skip config. Stale skips rot silently. Now Rector tells you which ones never matched: [WARNING] This skip is unused, it never matched any element. * SimplifyUselessVariableRector => */NonexistentUnused/* Clean config, free 😎

0 1 8 797 1

View Details

Tomas Votruba @VotrubaT

4 days ago

Just extract typical dev's workflow: 1) Pick an issue most likely to be fixed, while also bringint a value to the user 2) Extract reproducer test 3) Try to fix it, give it 10 min max (always enough for our issues, just to avoid to open-defined issues that make not enough sense) 4) open PR 5) make CI pass, give it 10 mins max 6) ping me once done or overtime 7) goto 1) 8) do max 1 issue per 20 mins (so I can review or improve this loop) I used agent this way to fix 40 out of 50 issues through my 20 repositories in a work week. While having fun, not going crazy and adding few features on the go.

Peter Yang @petergyang

4 days ago

I am pretty skeptical of building loops for everything because I'm paranoid about the agents creating slop if I'm not there to monitor what they're doing. What are some good loops to try for coding or regular knowledge work?

146 14 611 117K 566

0 1 6 1K 4

View Details

Tomas Votruba @VotrubaT

5 days ago

I'll share thoughts behind the question... If it's a tool, I don't know like PHPUnit, PHPStan, ECS, other coding standard tools or @rectorphp, there is a high chance its installed in couple thousands of open-source projects. Now the data mining part: 1) if it's in these projects, we can see it installed in composer.json 2) then we can see a config 3) in the config, there is first user's feedback 4) not all bugs reach project's issue tracker 5) we find let's say top 100 repositories on GitHub that use our project 6) then we check config for any ignore/skip/commented out behavior of our tool 7) behavior that should work, but it doesn't 8) it can look like: // Skip, false positive // Unreadable change // Breaks 9) then we extract this line, typically bound to specific file 10) then we ask our agent to check if it's edge case behavior or a bug 11) 3 out of 4 will be bugs 12) if it's considered bug by our agent, we ask him to fix it 13) then create a PR to our tool and make CI pass, cover with test fixture of course 14) the test fixture is already provided in GitHub repository skip line 15) make CI pass and merge 16) find next skipped line, repeat 17) once a month, release a new version of your tool and send PR to each repository where it fixes a skip 18) repeat untill all unreported bugs are fixed on top 1000 repositories on GitHub 19) there is high chance we've just fixed dozens or even hundreds of bugs that would never be reported, but all open-source and private projects can benefit from 20) 100 % automated with scripts + agents 21) profit 👌☺️

Tomas Votruba @VotrubaT

6 days ago

What if we could fix issues in open-source projects, before they got reported?

2 0 1 2K 0

1 1 3 2K 0

View Details

Artisan Weekly @artisan_weekly

a week ago

A nice thread running through one of the @LaravelLiveUK talks this morning - the "closed by default" principle, and a tour through how PHP has quietly become a much stricter, safer language since 5.0. Less permissive. Less error-prone. Better tooling. @rectorphp, Pint, @phpstan doing a lot of the heavy lifting. And if you haven't looked at the Type Coverage plugin for PHPStan or the rector-laravel package - both are worth your time, trust me! PHP's reputation hasn't always caught up with where the language actually is. Talks like we've seen this morning are a good reminder of how far it's come

0 2 6 530 0

View Details

Tomas Votruba @VotrubaT

6 days ago

I've just bumped @rectorphp dev repository PHP version PHP 8.4 to enjoy latest syntax. But you can still used it on PHP 7.4+ as a dependency 😉 How? tomasvotruba.com/blog/scope-and… (This trick comes handy for any codebase that needs an upgrade)

1 2 14 1K 4

View Details

Tomas Votruba @VotrubaT

6 days ago

The array_any/array_all functions are by far the most common applied improvement in code in PHP 8.4 🎉🎉🎉 Love it Thanks anyone who came with that RFC!

3 6 87 9K 20

View Details

Rector @rectorphp

a week ago

Big thanks to all contributors: @ruudk, @SanderMuller, @mbabker, @MrYamous, @florianhofsaessC24, @jquiaios, @u01jmg3 🙌

Rector @rectorphp

a week ago

🚀 Rector 2.4.6 is out! ✨ New RenameDeprecatedMethodCallRector - auto-renames calls from your @deprecated docblocks ✨ Brand new named args set ✨ Symfony 8 support enabled in composer-based 🐛 Many crash & dead-code fixes github.com/rectorphp/rect… #php #rector #refactoring

0 9 14 2K 2

0 0 2 373 0

View Details

Rector @rectorphp

a week ago

0 9 14 2K 2

View Details

Tomas Votruba @VotrubaT

2 weeks ago

Using an agent... ....what custom @rectorphp rule or @phpstan extension/rule have you created, that you would not have the nerves and the time to create manually?

7 3 6 2K 1

View Details

Rector @rectorphp

2 weeks ago

Do you have a rule set for your community/package? Consider adding composer-based sets and register them to @rectorphp core That way, these rules are loaded automatically based on composer.json versions @drupal set coming soon... github.com/rectorphp/rect…

0 1 1 262 0

View Details

Tomas Votruba @VotrubaT

2 weeks ago

Would you merge such a PR without deep review of all ~300 files? We do. Because it's not AI, nor human. It's tokens (T_*, not AI) and AST. 100 % trust, 0 % hallucinations

0 2 12 1K 0

View Details

Tomas Votruba @VotrubaT

2 weeks ago

I've just realized we didn't have an offical way to sponsor @rectorphp ... Fixed it first task today ⬇️ If you're a company using Rector and saving you time and money, consider giving back to support on-going development🙏 github.com/sponsors/recto…

Conao3 @conao_3

3 weeks ago

私が所属しているトヨクモで、Thanks OSS Award 2026年度上半期の公開を行いました! 1年間で約1000万円のOSSへの寄付活動を継続して行っています。今期は特にVite関連の貢献から @sapphi_red さん、 @boshen_c

6 24 52 19K 4

0 7 11 2K 1

View Details

Tomas Votruba @VotrubaT

2 weeks ago

Symplify PHPStan rules 14.11.0 just dropped 🎉 2 lines in your phpstan.neon, two new safety nets: * ctor: true # use constructors, not setter soup * mocks: true # spot fragile PHPUnit mocks Bonus: smarter return types for Symfony, Laravel & path functions - now built in. PHP 8.4 ✅ Check the full release with examples ⬇️ github.com/symplify/phpst…

1 7 27 1K 13

View Details

Rector @rectorphp

2 weeks ago

Rector is now on GitHub Sponsors! 🎉 Rector upgrades and refactors PHP, frameworks and keeps technical debt away💙 Work that takes attention and time, done automatically: in CI or CLI, for free If Rector saves your team time, consider sponsoring its development: 👉 github.com/sponsors/recto… Your sponsorship keeps it free, open, and actively maintained 💙

0 3 8 466 0

View Details

Tomas Votruba @VotrubaT

3 weeks ago

PHPStan core is just the start. I built a searchable index of 263 community @phpstan rules from 11 popular packages - each with its class name, what it catches, and wrong/correct examples. Goldmine for tightening your PHP codebase 👇 tomasvotruba.com/phpstan-rules-…