From 485c1f6b0dc655b5e53de1242b77f9403f29aebd Mon Sep 17 00:00:00 2001 From: Johan Vlaar Date: Thu, 6 Mar 2025 10:29:34 +0100 Subject: [PATCH] Define all composer based options in correct order --- resources/docs/composer-based-sets.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/resources/docs/composer-based-sets.md b/resources/docs/composer-based-sets.md index 802ee37c2..10ca7c7d0 100644 --- a/resources/docs/composer-based-sets.md +++ b/resources/docs/composer-based-sets.md @@ -4,10 +4,10 @@ Projects like Symfony, Doctrine, Twig or Laravel have lots of versions. Instead use Rector\Config\RectorConfig; return RectorConfig::configure() - ->withComposerBased(doctrine: true, twig: true, symfony: true); + ->withComposerBased(twig: true, doctrine: true, phpunit: true, symfony: true); ``` -* Rector should look into installed `composer.json` version of `twig/twig`, `doctrine/*` and `symfony/*` +* Rector should look into installed `composer.json` version of `twig/twig`, `doctrine/*`, `phpunit/phpunit` and `symfony/*` * then it picks all sets that are relevant to your specific installed versions * and run those