Description
I find the @typescript-eslint/strict-boolean-expressions lint rule a bit painful and have turned it off in Encoda because it makes heavy use of expressions like variable && variable.prop and variable || 'default'.
I cant' find a good rationale for this rule, especially for null and undefined. The TSLint docs, whence this rule came, offer no insight: https://palantir.github.io/tslint/rules/strict-boolean-expressions/.
Others also think this rule is too strict by default typescript-eslint/typescript-eslint#698. I suggest that until some of those options are available that we remove this rule.