-
Notifications
You must be signed in to change notification settings - Fork 446
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
Improve wording of the NonexistentOffset, BooleanAndConstantConditionRule and BooleanOrConstantConditionRule #1882
Conversation
9248337
to
bdd2829
Compare
This pull request has been marked as ready for review. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We can't do this because it'd break existing baselines. We can do this only with a new bleedingEdge toggle.
A similar thing could be fixed in BooleanAndConstantConditionRule and BooleanOrConstantConditionRule where the message still uses &&
and ||
even for logical and
and or
operators.
new bleeding edge toggle kind of means that it will get into the next major automatically, right? |
Exactly, and no rebase nightmare either. |
Yeah, I'll update the PR |
32abba4
to
50b4817
Compare
50b4817
to
96be48f
Compare
Done
Done |
Thank you. |
Related to phpstan/phpstan#8187 (comment)
I feel like
is confusing and
is better.