Rector `--only` seems to interact weirdly with the cache

[theofidry]

Bug Report

Subject	Details
Rector version	2.2.11

Minimal PHP Code Causing Issue

While working on alice, I executed:

vendor-bin/rector/bin/rector --dry-run
vendor-bin/rector/bin/rector --only=GetDebugTypeRector --dry-run # did not show any change
vendor-bin/rector/bin/rector --only=GetDebugTypeRector --dry-run --clear-cache # showed up changes!

Expected Behaviour

I'm ensure how the cache works there, but I expect using --only=Rule to apply the rule on any relevant file, with our without a clean cache.

[samsonasik]

Yeah, that's expected, when using --only, the --clear-cache should always be used. See the whole discussion on #9485

[theofidry]

Ha I see.

I did think there is a lot that could be done and is tricky on the rector cache...

I assume pushing another cache entry is not that simple? Would disabling the cache for --only be an option then?

[samsonasik]

Yeah, that complicated per original kick of PR:

• [Configuration] Make --only to force clear cache to ensure next normal run start from fresh state rector-src#7641

user will do: run --only, then run normal rector, then run --only again, that the "last" flag need to be saved to another cache

[theofidry]

Indeed that would require more primitives with the cache, e.g. defining whether to use it at all or add additional parameters for the cache keys... Which obviously is a lot more work.

Feel free to close it if it's not an issue that is planned to be fixed in a foreseeable future.

[samsonasik]

Yes, thank you for understanding ;)