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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
DX: Include self_static_accessor fixer in PhpCsFixer set #6882
DX: Include self_static_accessor fixer in PhpCsFixer set #6882
Conversation
Pull Request Test Coverage Report for Build 4612059529
馃挍 - Coveralls |
Overall that's the goal, but also that's generating conflicts. should we limit amount of PRs first? |
I don't see it happen soon enough 馃槄. I believe it would be better to apply it and then it's really easy to rebase PRs end resolve conflicts (because Fixer will fix it anyway, regardless of how conflict is resolved). Personally I am not afraid of invasive changes and I even could help with rebasing things, if I had enough project role to do it 馃槈. |
I remember we had this discussion 2 years ago with the same plan - to lower the number of open PRs. Let's fix the conflict and merge it, any conflicts it will introduce would be easy to resolve. |
352c3cb
to
f0792f8
Compare
Thank you @Wirone |
PHPStorm underlines all of these
static::
calls in tests and I thought it would be good to include this fixer in thePhpCsFixer
ruleset to keep the code clean from such redundant usage 馃檪. Let me know what you think.