Incorrect indentation for single line if/for/while/etc, multiline chaining statements etc

[johanolofsson]

I am experiencing some weird indentation issues. Not using any plugins to prettify or similar.

if (condition) {
    return; // <-- correct indentation
}

if(condition)
return; // <-- incorrect indentation

Some ppl claim this should be avoided. I don't agree. Using pair of { } for simple early exits messes up code. Putting the return on the end of the same line can be hard to read if the condition is long.
This is not exclusive to return. Applies to all single lines.

same problems apply to for, while, etc.

var transformedValues =
originalValues <-- incorrect should be indented one level.
.where(condition) <-- incorrect, should be indented two levels.
.select(transform); <-- incorrect, should be indented two levels. 

function someFunction() {
    callToSomeOtherFunction(
         variableWithLongNameWhichRequiresASeparateLine,
         anotherVariableWithLongNameWhichRequiresASeparateLine);
    }  <-- incorrect should not be indented.
    function ... <-- incorrect the rest of the file is indented. 

[johanolofsson]

Thx for picking this up! Btw, it applies to typescript as well.

class Foo {
    public bar(x: number): void {
        if(x == 0)
        return; // <-- incorrect
    }
}

[Spongman]

also related, after typing, the code looks like this:

if (condition)
return;

but after 'Format Document' the indentation is correct:

if (condition)
  return;

but if you put the cursor after the ; and hit ENTER, the cursor is incorrectly indented:

if (condition)
  return;
  |  <-- cursor is here, should be in column zero.

[rickrankin]

This also applies C/C++/D, as well. Probably anything derived from C syntax.

[ahfeel]

Also applies to PHP, very very frustrating :( Anybody figured out a solution or an extension that fixes this ?

[johanolofsson]

None as far as I know, the fact that this has not yet been addressed is kind of weird. Seems to me like a very fundamental part of a decent code editor.

I'm starting to wonder if this is actually a case of opinion where the responsible developers simply don't agree with this way of avoiding { } and therefore just happens to forget about it? Microsoft, pls prove me wrong on this!

[stanislavdavid]

There is even bug with this code:

if (condition) { some code in 1 line }
    next command wrongly intended