Expected { after 'if' condition even with single lines

[jonaswindey]

Using standard@8.6.0, the following code fails:

const test = false
if (test)
  console.log(false)
else
  console.log(true)

Error:

  /Users/jonas/Development/sandbox/test/test.js:2:1: Expected { after 'if' condition.
  /Users/jonas/Development/sandbox/test/test.js:4:1: Expected { after 'else'.

whereas this one works:

const test = false
if (test) console.log(false)
else console.log(true)

Could be related to #664 , but the issue has been closed and this issue still exists

This makes it difficult to use single-line if blocks when they are too long to fit on the same line.

[LinusU]

I think this is intentional, I at least prefer this behaviour

[jonaswindey]

The error says Expected { after 'if' condition.

If I add the curly brackets like this:

const test = false
if (test) {
  console.log(false)
}
else {
  console.log(true)
}

It says there's an unnecessary { after if (due to being a single line)

This is confusing to say the least.

What do you do then when you have a single line after an if condition that is too long and you want to put it on the next line?

[LinusU]

I think that it's like so,

single line:

if (thisIsAll) onOneLine()

multiple lines:

if (thisIsActually)
  twoLine()

What do you do then when you have a single line after an if condition that is too long and you want to put it on the next line?

You put brackets around it

[dcousens]

@jonaswindey

Single line

const test = false
if (test) console.log(false)
else console.log(true)

Multi line

const test = false
if (test) {
  console.log(false)
} else {
  console.log(true)
}

As you pointed out, other [non-standard] formatting of these statements will throw respective errors.

[jonaswindey]

Ok, I guess that rule changed than? I remember that

const test = false
if (test) {
  console.log(false)
} else {
  console.log(true)
}

Gave Unnecessary { after 'if' condition. because it only contained one line (or other ifs)

Thanks for clarifying