Skip to content
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

Merged
merged 5 commits into from
Aug 11, 2016
Merged

How to polish code, eg: OC\User #25767

merged 5 commits into from
Aug 11, 2016

Conversation

butonic
Copy link
Member

@butonic butonic commented Aug 11, 2016

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:
unbenannt

unbenannt

Before
unbenannt

After
unbenannt

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

@mention-bot
Copy link

@butonic, thanks for your PR! By analyzing the annotation information on this pull request, we identified @rullzer, @LukasReschke and @ChristophWurst to be potential reviewers

@DeepDiver1975
Copy link
Member

looks good 👍

@DeepDiver1975
Copy link
Member

DeepDiver1975 commented Aug 11, 2016

Could you also add the missing PHPDoc?

@butonic
Copy link
Member Author

butonic commented Aug 11, 2016

Sure thing.

@PVince81
Copy link
Contributor

Looks good, OC didn't explode on my env like it sometimes does with use statements 👍

@PVince81 PVince81 merged commit 3132835 into master Aug 11, 2016
@PVince81 PVince81 deleted the polish-user-code branch August 11, 2016 19:03
@tflidd
Copy link
Contributor

tflidd commented Aug 19, 2016

@butonic Do you know if there are good free alternatives to PHPStorm?

@DeepDiver1975
Copy link
Member

@tflidd jentbrains offer a free of charge open source license - https://www.jetbrains.com/buy/opensource/

@lock
Copy link

lock bot commented Aug 4, 2019

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.

@lock lock bot locked as resolved and limited conversation to collaborators Aug 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants