selectively disabling rules on a case-by-case basis. maybe. about standard HOT 6 CLOSED

Hahahah, nice.

I just added documentation for how to ignore specific warnings. See: https://github.com/feross/standard/blob/master/README.md#how-do-i-hide-a-certain-warning

from standard.

The most useful use-case for == is to check if a value is equal to undefined or null, like this:

if (obj == null) {
  // obj is `null` or `undefined`
}

Which is nicer than:

if (obj === null || obj === undefined) {
  // obj is `null` or `undefined`
}

JavaScript Standard Style allows == null out-of-the-box without needing to hide any warnings. If you want to use == to compare to objects other than null, you'll need to ignore the warning that generates.

from standard.

+1 about ==, this is the one case that is really usefull! You can't just use === everywhere, but you should know the difference.

from standard.

Since the common case of == null is allowed by default, and there's a way to hide the warnings in other cases, I'm going to close this issue now. But you can feel free to continue discussion if there's interest.

from standard.

Perfect. That was the exact usecase.

from standard.

Yay!

from standard.