`if` statements – one line vs. one expression

Until I started using ESLint with your configuration I saw nothing against the rules in this:

$ cat if.js
const [one, two] = [1, 2];

if (one !== two) throw new Error(
  'One does not equal two'
);

But ESLint does:

$ eslint if.js 

if.js
  3:0  error  Expected { after 'if' condition  curly

✖ 1 problem (1 error, 0 warnings)

Is this intended? In my opinion the pattern I’ve been using is explicit – and more readable than this:

if (one !== two) {
  throw new Error(
    'One does not equal two'
  );
}

The parens form a visual brace-like block much like in #438.

[ljharb]

@englishextra your comment is both unhelpful and condescending; I’m going to delete it. Please be respectful in the future.

[tomek-he-him]

Yeah, both of your examples look good with a five-word error message. I use my variant because my error messages tend to get long and descriptive – much like in the #438 example.

So it’s a question of:

if (one !== two) throw new Error(
  'One does not equal two. This error is common when you try to determine if ' +
  'the number `1` has the same value as the number `2`. Please try again, or ' +
  '– if that fails – get in touch with your administrator.'
);

vs.

if (one !== two) throw new Error('One does not equal two. This error is common when you try to determine if the number `1` has the same value as the number `2`. Please try again, or – if that fails – get in touch with your administrator.');

vs.

if (one !== two) {
  throw new Error(
    'One does not equal two. This error is common when you try to determine ' +
    'if the number `1` has the same value as the number `2`. Please try ' +
    'again, or – if that fails – get in touch with your administrator.'
  );
}

The second is obviously invalid. And I do prefer the first to the last – for the sake of readability.

But feel free to close the issue if you don’t think my point makes sense – I’ll adapt.