Auto closing brackets should try to balance brackets

[vsccarl]

• VSCode Version: 1.1.0-alpha
• OS Version: Windows 10

Steps to Reproduce:

1. Open launch.json or create one
2. Delete the opening bracket { under configurations
3. Re-type the opening bracket

Auto-complete adds in a closing bracket when the closing bracket at the end of the config is showing an error. It would make sense that bracket auto-complete would know that there is an open bracket and to not add the closing bracket at the top.

[alexdima]

Auto closing brackets are not taking language semantics into account

[vscodebot]

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[schokotets]

Where would one upvote the issue? Just as I did, by giving a thumbs-up on the bot's message?
I'd really like this to be implemented for #13982

[vscodebot]

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.

Happy Coding

[rmunn]

@schokotets You upvote an issue by leaving a thumbs-up on the first comment (the issue description), not on the bot's message.

[vscodebot]

🙂 This feature request received a sufficient number of community upvotes and we moved it to our backlog. To learn more about how we handle feature requests, please see our documentation.

Happy Coding!

[rhyek]

When implemented this new option could potentially replace the current "beforeWhitespace". As of now, typing in a TypeScript file has the following inconsistent behaviors:

Scenario 1

• with text someFunction;
• type a ( before ;
• result is someFunction(;

Scenario 2

• with text someFunction);
• type a ( before )
• result is someFunction());

Scenario 3

• with text someFunctionsomeParam);
• type a ( before someParam
• result is someFunction(someParam);

Only the last scenario produces the expected behavior and in the previous two are both undesired (from a practical standpoint) and inconsistent behaviors.

vsc: 1.60.1
macos big sur

[toni-neurosc]

Any progress on this? I'm surprised this isn't still implemented.