Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Tabs & Spaces before braces in control flow statements? #31272

Closed
azarus opened this issue Jul 23, 2017 · 5 comments
Closed

Tabs & Spaces before braces in control flow statements? #31272

azarus opened this issue Jul 23, 2017 · 5 comments
Assignees
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues

Comments

@azarus
Copy link

azarus commented Jul 23, 2017

Enter after typing a control flow statement puts spaces or tab.

Fucked up control flow

Typing an if statement
causes code to look like this:

if(true)
    {
// Why is there a tab?
    }

Note the tabs before the braces?

It should work like this

if(true)
{
 // No tab before the braces!
}

I have no idea if this is an option or not, but if this is an option i'd recommend to remove it immidiately because that is just "jesus what the hell is that?". I have no idea what happened it started to act this weird after updating to the latest version.

More here:

Fucked up braces

@vscodebot vscodebot bot added the javascript JavaScript support issues label Jul 23, 2017
@azarus
Copy link
Author

azarus commented Jul 23, 2017

Downgrading to the 2017 may version and disabling the bullshit updates fixed the issue. Thanks a lot for driving me crazy with the awesome updates. In the mean time good luck figuring out what caused the issue listed above.

@mjbvz mjbvz added the *duplicate Issue identified as a duplicate of another issue(s) label Jul 24, 2017
@mjbvz
Copy link
Collaborator

mjbvz commented Jul 24, 2017

Duplicate of #30933

Please do not add unnecessary side snark when reporting issues: https://opensource.microsoft.com/codeofconduct/

@mjbvz mjbvz marked this as a duplicate of #30933 Jul 24, 2017
@mjbvz mjbvz closed this as completed Jul 24, 2017
@simonl65
Copy link

@mjbvz There's a large number of issues raised for this and many seem to be getting closed with reference to others. This needs to be fixed

@davidstlyoui
Copy link

Ok so we have a big problem here... Javascript is impossible to use right now with 1.14 because of this bug. There are like 5 tickets on this, and they are all closed without a fix. All marked as duplicate with each other. Where is the REAL ticket? This is a blocker!
#30933 is closed, with only "yo just used previous version".

@mjbvz
Copy link
Collaborator

mjbvz commented Jul 31, 2017

As already noted, this is tracked by #30933

@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 17, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*duplicate Issue identified as a duplicate of another issue(s) javascript JavaScript support issues
Projects
None yet
Development

No branches or pull requests

5 participants