List rules/rectors that were executed

[cweiske]

I'm using rector 0.12.23 with typo3-rector which provides pre-defined sets. One rule/rector is not applied, and I want to see if the rule is loaded at all in the set.

I would have thought that --debug or -vvv would give me this information, but it does not.

How can I quickly find out which rules have been loaded, without inspecting the source code of the set and drilling down deeper into the files?

[TomasVotruba]

Hi, we've added rule + file debug output in the latest dev-main when you run it with --debug option.
Try that on single file. That should give you the full list of run rules.

[samsonasik]

@TomasVotruba it seems --debug doesn't show anything, while -vvv show it:

with --debug

bin/rector process src/Config/  --clear-cache --debug

                                                                                                                        
 [OK] Rector is done!                                                                                                                                                                                                                 

with -vvv

bin/rector process src/Config/  --clear-cache -vvv |more
src/Config/Loader/ConfigureCallMergingLoaderFactory.php
[file] src/Config/Loader/ConfigureCallMergingLoaderFactory.php
[rule] Rector\DeadCode\Rector\Node\RemoveNonExistingVarAnnotationRector

[file] src/Config/Loader/ConfigureCallMergingLoaderFactory.php
[rule] Rector\CodingStyle\Rector\Stmt\NewlineAfterStatementRector

[file] src/Config/Loader/ConfigureCallMergingLoaderFactory.php
[rule] Rector\DeadCode\Rector\Node\RemoveNonExistingVarAnnotationRector

[file] src/Config/Loader/ConfigureCallMergingLoaderFactory.php
[rule] Rector\CodingStyle\Rector\Stmt\NewlineAfterStatementRector

[TomasVotruba]

Hm 🤔 Could check what is wrong there?

[samsonasik]

I will try.

[samsonasik]

It seems it because of parallel process, when it run on non-parallel, it working ok.

[samsonasik]

rectorphp/rector-src#2307