Create rector for transforming Laravel validation rules to a prettier format

[sashabeton]

#1766

This is the first simplest version that covers the most of situations, but it is not fully flexible.
Now it works, but it can be improved. I tried to implement some features, but I didn't succeed.

1. Is there a way to include additional use statement instead of using full namespace? I mean I want to split \Illuminate\Validation\Rule::exists(...) into a use \Illuminate\Validation\Rule; statement and Rule::exists(...) statement.

2. Is there a way to split each array element to the new line? All rules in one line don't look so beautiful.

[TomasVotruba]

Looks very robust, good job!

Looks at local $this-> methods, there are many helpers that you can leverage.

To both your points, this is job of coding standard tool, as they handle it better (AST sucks at coding standard by technology limits) and every project has different ruleset. Just see ecs.yaml in this project

[sashabeton]

No ideas why isType() method is undefined.. This test passes locally

[TomasVotruba]

Rebase on master, there were some method name change

[TomasVotruba]

I use this approach to update the forks: https://help.github.com/en/articles/syncing-a-fork

First it's a bit hard to understand, but then works pretty well 👍

[TomasVotruba]

Could you rebase one more time?
It's ready then

[sashabeton]

Thank you too much for help!

Do I need to do something more?

[TomasVotruba]

CI passes, great 👍

Could you add 1-2 more test that would cover some other/skipped cases?

[sashabeton]

I've created all cases that this rector can process, in future I'll try to expand its functionality and add other :)

[TomasVotruba]

Thank you for your contribution!