We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Why should this rule be added? Share links to existing discussion about what the community thinks about this. Rule request: No explicit == true or == false #1502 (comment)
== true
== false
Provide several examples of what would and wouldn't trigger violations.
if someObj == someObj {} // always true if objA != objA {} // always false
This would not trigger even though they might have the same value. :
let someObj2 = someObj if someObj2 == someObj {} // always true
Should the rule be configurable, if so what parameters should be configurable? probably not.
Should the rule be opt-in or enabled by default? Why? See README.md for guidelines on when to mark a rule as opt-in. Probably Default if fast enough.
The text was updated successfully, but these errors were encountered:
Duplicate of #1371?
Sorry, something went wrong.
ha! totally, I just could not find it.
No branches or pull requests
Rule Request
Why should this rule be added? Share links to existing discussion about what
the community thinks about this.
Rule request: No explicit
== true
or== false
#1502 (comment)Provide several examples of what would and wouldn't trigger violations.
This would not trigger even though they might have the same value. :
Should the rule be configurable, if so what parameters should be configurable?
probably not.
Should the rule be opt-in or enabled by default? Why?
See README.md for guidelines on when to mark a
rule as opt-in.
Probably Default if fast enough.
The text was updated successfully, but these errors were encountered: