Incorrect automatic caret indentation on a new line after a statement without an opening '{'.

[rdxroman]

After writing the following line
if (someCondition)
and then pressing the 'enter' key, the caret position in the new line will have the same indentation as the 'if' statement, which results in incorrect indentation.

Example:
Caret position is represented by the '|' sign.
Actual Result:

if (someCondition)
|

Expected Result:

if (someCondition)
    |

Same happens for other statements such as 'for' etc.

[sean-mcmanus]

This is currently "by design". We don't add tabs after a newline is entered. Even typescript doesn't add a tab in these scenarios in VS Code. VS 2017 does add the tab though, so we'll probably support this eventually.

[rdxroman]

If I enter the following:
if (someCondition) {
and press the 'enter' key, the result will be:

if (someCondition) {
    |

Is it considered a different scenario due to the explicit scope opening?

[sean-mcmanus]

Ah, I see. Yeah, the tab is being added by VS Code itself and not our extension. Using Enter after { is treated as started a scope so it is able to auto-indent, but whatever code is handling this doesn't understand one-line blocks that require indentation. Since the issue repros with Typescript and both languages share the same if/for/etc. statements, maybe VS Code itself could implement a fix. Maye this VS Code issue would address it: microsoft/vscode#16998 .

[sean-mcmanus]

We'll track this with #883