A way to stop rector from changing unaffected files by importNames parameter about rector HOT 3 CLOSED

I think you can have 2 kind of configs for that, eg:

• rector.php without import
• rector-with-import.php with import

then, in your rector-with-import.php, you can do:

return static function (RectorConfig $rectorConfig): void {
     $rectorConfig->import(__DIR__ . '/rector.php');
     $rectorConfig->importNames();
};

so you can run rector-with-import.php on separate command when you want to change it:

vendor/bin/rector process --config rector-with-import.php

or vice versa so you can review as another individual change.

from rector.

@samsonasik Sorry, but I don't understand how exactly it helps in my case.

If I want to go throughout the code applying a rule that changes interface usage to an attribute (in my case - MessageHandlerInterfaceToAttributeRector), it will either

A) [without importNames()] Update only the files I need but use annotation with the full namespace like this:

#[\Symfony\Component\Messenger\Attribute\AsMessageHandler]
class Foo
{
}

B) [with importNames()] It will add correct annotation with the short class name:

use Symfony\Component\Messenger\Attribute\AsMessageHandler;

#[AsMessageHandler]
class Foo
{
}

But it will also change full class name usages throughout all my code, which is huge.

So, there is no option C) at the moment, where I'd get short class for the attribute, and it won't change all other files which I didn't want to affect. I don't understand how having 2 separate config files may help me.

from rector.

It was removed due to avoid too detailed setup and making ambiguous code, see PR:

• rectorphp/rector-src#3132

You can have as many config as needed for your use case, then run separately with --config argument in CLI.

Thank you for understanding.

from rector.