Skip to content

Define all composer based options in correct order #2897

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
TomasVotruba merged 1 commit into from
Mar 6, 2025
Merged

Define all composer based options in correct order #2897

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions resources/docs/composer-based-sets.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down