Sort named arguments breaks file

[hschimpf]

Bug Report

Subject	Details
Rector version	v2.2.6

When Rector tries to sort named arguments, it breaks the PHP file.

Minimal PHP Code Causing Issue

https://getrector.com/demo/b48e52e8-c0d7-4115-9923-e6b008ef838a

Expected Behaviour

The named arguments should be sorted without breaking the file.

[samsonasik]

That's seems PHPStan internal printer issue which modify ParametersAcceptor result, I was trying to fix it, but can't get the solution yet, see PR:

• [Printer] Fixture crash on named argument usage on array_map() due to unpack arg flipped rector-src#7399

[samsonasik]

Hi @ondrejmirtes , could you help on PHPStan printer on this? When only printing array_map() with flipped order of named argument, it already error, even no rule applied.

see:

sorted (works) : https://getrector.com/demo/1b5551b2-0fb4-4223-aed9-3853269204f2
not sorted: (invalid print): https://getrector.com/demo/d795a284-c4a1-4c25-9936-e513c7e86f93

-        $result = array_map(array: $items, callback: fn ($item) => $item * 2);
+        $result = array_map(array: $items, callback: fn ($item) => $item * 2 array: $items, callback: fn ($item) => $item * 2);

it doubled the callback argument, cause php error in result, see https://3v4l.org/d33RY

It somehow in PHPStan internal process, the sorting is too early applied, then repeated on printing when call pArray() on PHP-Parser Printer.

Thank you.

[ondrejmirtes]

Hey, I'm pretty sure it's a bug in Rector and I can't help you with that.

If you isolate the problem to a simple code that uses PHPStan's API I might be able to help you.

[samsonasik]

@ondrejmirtes the sort named arg seems happen on PHPStan's PHPStan\Analyser\NodeScopeResolver::processNodes() when there is isVariadic parameter on its variant, which happen on array_map() when named parameter passed arg are flipped, so on printing, it duplicated, I am trying to check phpstan code, but it got phpstan.phar which of course not accessible.

[ondrejmirtes]

Please show a piece of code how are you calling PHPStan, what you're doing with the results, what are you getting and what are you expecting instead.

Insides of phpstan.phar can be comfortably inspected with PhpStorm.