-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
Rule request: identical operands in comparison operator rule #1371
Comments
I think instead of matching anything |
@marcelofabri Do you think this rule should be on by default? |
Seems like a reasonable place to start to me! OSSCheck would undoubtedly catch if this produces common false positives. |
@jpsim You had an idea of more rules around this sort of line of thinking? (I think I remember you posted something on twitter with a document that pointed out some of these common issues.) |
Just lost a half hour to this exact issue. Came here to post my +1. |
In addition to the basic operators above we should also include: surprisingly Logical NOT (!a) can be essentially ignored which is good since this could have been tripped the unwrap operator. ternary conditional operator: |
Hey - looks like you forgot to add a T:* label - could you please add one? |
See #1368 for more history.
The text was updated successfully, but these errors were encountered: