-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
How to polish code, eg: OC\User #25767
Conversation
@butonic, thanks for your PR! By analyzing the annotation information on this pull request, we identified @rullzer, @LukasReschke and @ChristophWurst to be potential reviewers |
looks good 👍 |
Could you also add the missing PHPDoc? |
Sure thing. |
936b76f
to
de0b02e
Compare
Looks good, OC didn't explode on my env like it sometimes does with |
@butonic Do you know if there are good free alternatives to PHPStorm? |
@tflidd jentbrains offer a free of charge open source license - https://www.jetbrains.com/buy/opensource/ |
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
This PR serves as an example for polishing some of the issues that PHPStorm spits out when pressing "Inspect Code ...". They should be limited to a namespace to keep it reviewable.
Inspecting a subfolder:

Before

After

The four commits all address a single type of code smell. Feel free to just submit PRs for a single smell.