New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace explicit __invoke
call with regular call syntax
#7981
Comments
Is this feasible, are you sure |
What do you mean? As long as the |
You are right - https://3v4l.org/fPaLC - 👍. I thought |
It does not matter, |
It matters - https://3v4l.org/AYFu3, but I am neutral if it should be risky or not. |
Ahhh, this way 😅. I think there are 2 possible paths:
In general, seems like a job more for a Rector than Fixer. |
IMO the fixer is pretty simple to implement, and since the risky situation is very unlikely, I think it's fine to have it in PHP CS Fixer. |
@julienfalque of course, I am not against this rule, I just think it will be risky anyway, since we just can't ensure proper context (including inheritance). Side question: should the rule support 2-way standardisation? Or we consider using short invocation as a promoted standard? |
Fixing from |
@julienfalque in context of Wirone#5 (comment) , do you want to keep this ticket open ? |
@keradus Yes, the situations are not the same. We may prefer to avoid |
Feature request
Link to Discussion where feature request was formed
No response
Contribution Checks
The text was updated successfully, but these errors were encountered: