-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Remove underscores from private/protected members names #3007
Remove underscores from private/protected members names #3007
Conversation
0a06bbe
to
27c3af7
Compare
27c3af7
to
2c1cf8a
Compare
Restarted the failing build. Although not a blocker, can you please look into the CS issues? We currently have a rule that modified code should follow Doctrine CS (even if rest of the code doesn't yet). |
@Majkl578 I believe we could ignore the code style issues for massive automated changes like this as long as they don't introduce new issues. Or maybe whitespace/alignment issues could be fixed here as well. What kind of a BC layer do you have in mind? For protected methods, we could have the deprecated old methods which invoke the new ones. But what about properties? |
Benefits here are too marginal to consider the patch, compared to massive BC concerns. Closing as |
How about reconsidering what really needs to be protected and for those provide final protected getter (and make fields private)? |
@Majkl578 anything that we can make |
Besides the above, we still can fix private methods and properties and protected methods and properties in the non-abstract test classes. As for private/protected as such, there's also lack of consistency across the codebase. For instance, |
Closes #3004