2020-10-08
2076
#php#wordpress
Leonardo Losoviz
26442
Oct 8, 2020 â‹… 7 min read

Transpiling PHP code from 8.0 to 7.x via Rector

Leonardo Losoviz Freelance developer and writer, with an ongoing quest to integrate innovative paradigms into existing PHP frameworks, and unify all of them into a single mental model.

Recent posts:

i tried kiro and here is what i learned

I tried out Kiro: Here’s what I learned

Check out Kiro, AWS’s AI-powered IDE, see what makes it different from other AI coding tools, and explore whether it lives up to the hype.

Elijah Asaolu
Aug 28, 2025 â‹… 5 min read
Go Design Pattern Article Image With Logo

Why Go design patterns still matter

Here’s how three design patterns solved our Go microservices scaling problems without sacrificing simplicity.

Peter Aideloje
Aug 28, 2025 â‹… 2 min read
how to protect your ai agent from prompt injection attacks

How to protect your AI agent from prompt injection attacks

Explore six principled design patterns (with real-world examples) to help you protect your LLM agents from prompt injection attacks.

Rosario De Chiara
Aug 27, 2025 â‹… 5 min read
Don’t Let AI Erase The Next Generation Of Dev Leaders

Don’t let AI erase the next generation of dev leaders

As AI tools take over more routine coding work, some companies are cutting early-career dev roles — a short-sighted move that could quietly erode the next generation of tech leaders if we aren’t careful.

Jack Herrington
Aug 26, 2025 â‹… 6 min read
View all posts

4 Replies to "Transpiling PHP code from 8.0 to 7.x via Rector"

  1. Awesome, thanks for the post! And you’re totally right, I’m a WordPress plug-in and theme developer and I’ve been wanting to use php 7 since day one. The only thing that worries me is testing. How will we know the production code works as expected? Will we have to write two sets of tests for each codebase?

  2. My idea is to run some PHP tool to analyze the downgraded code, using PHP 7.1. If the transpiling failed and PHP 7.2 was left behind, then this process will fail.

    I describe this strategy here: https://graphql-api.com/blog/graphql-api-for-wp-is-now-scoped-thanks-to-php-scoper/#heading-testing (his blog post is about scoping the code, but either scoping or downgrading, the idea is the same).

    As for what library to use, you can still use Rector, but since it requires PHP 7.3+, you must use its downgraded to PHP 7.1 version from here: https://github.com/rectorphp/rector-php71

  3. It’s me again! What’s your experience with named arguments? Have you been able to compile named arguments to positional arguments? The DowngradeNamedArgumentRector seems to only downgrade arguments from class methods. And only form the classes defined in the source code. I’m guessing it’s not possible to downgrade named arguments when using bult in functions or third party APIs like WordPress, right?

    1. So my understanding is that the classes and functions need to be loaded in memory at the time Rector is running. Any ideas on this? It seems an extremely hard thing to do considering WordPress mixes initialization logic with function definitions. Which seems like a shame, because if there’s an API we could benefit from using named arguments it’s the main WordPress Core.

Leave a Reply