strict-boolean-expressions wrongly reports on short-circuit expressions

[karfau]

In our current code base we can not use v0.0.4, because the rule strict-boolean-expressions (wich is useful to prevent issues when using strings and numbers as part of boolean expressions,) doesn't know about short-circuit syntax that is heavily used in JSX.
It reports that the last part of the expression is always true.

We either want to fix the tslint rule or create a more lightweight one that just reports usages of number and string values in such expressions.

[karfau]

@YEver please check if the description is matching with what we discussed, or if you want to add anything.

[karfau]

PR #81 contains the following:

• [new-rule-option]strict-boolean-expressions accepts ignore-rhs option to disable checking the right-hand side of the && and || operators as strictly boolean. (#​4159)

Which would allow us to close this issue

[karfau]

The issue can not be closed, the rule still reports all kinds of cases that we believe are not a problem due too the fact that objects and functions are truthy compared to null or undefined, this doesn't seem to be configurable right now.