Hi, thanks for the feature.
What is the use case here?

The use case is a change in order of parameters in an external package. In my case a child class calls a parent's method which is imported from a package. For example:

abstract class ParentClass
{
    public function call(int $param1, string $param2): void
    {
    }
}

becomes

abstract class ParentClass
{
    public function call(string $param2, int $param1): void
    {
    }
}

So the child class can be refactored automatically from

class ChildClass extends ParentClass
{
    public function callParent(): void
    {
        $this->call(123, 'some string');
    }
}

to

class ChildClass extends ParentClass
{
    public function callParent(): void
    {
        $this->call('some string', 123);
    }
}

But I generalised it to the method call, not only in the parent-child case.

General rules should be useful in an open-source packages, so we can add it in publicly used sets. Otherwise it's better to use simply IDE.

What os package has this change?

Actually it's not an open-source package, it's internal to my company. I thought it would be useful elsewhere. But I didn't know the rules are primarily made for the public sets. Sorry for the miscomprehension!

Actually it's not an open-source package, it's internal to my company. I thought it would be useful elsewhere. But I didn't know the rules are primarily made for the public sets. Sorry for the miscomprehension!

Well said, let's give it a try if this will catch up 👍 Thank you

Hi @gaydamakha,

I've noticed this rule could lead to infinite argument swaps on each run. Which would condition to run Rector just once and make usage confusing.

Instead, it's better to create a custom rule for these swaps and check e.g. argument type and variable name to match their new positions. Only that way the rule can be idempotent and usable in CI 👍

Ref #4766