Typescript: javascript format: disable insert space inside curly braces

[mjbvz]

_From @BenjaVR on April 5, 2017 11:13_

Since there are already some javascript.format.insertSpace... settings available in VSCode, I have a suggestion to add another one.

When I import with curly braces, a space is added before and after the "imported word":

While doing the same in WebStorm:

VSCode also inserts a space to returns:

Webstorm does provide a setting for this: "spaces within ES6 import/export braces" to toggle this behaviour. Is it possible to add this setting to VSCode as well?

_Copied from original issue: Microsoft/vscode#23929_

[aluanhaddad]

A typescript.format.insertSpace setting would also be most welcome.

[mzvast]

Is there any progress about this feature?

[aluanhaddad]

@mzvast it is implemented.

In VS Code, go to preferences (workspace or global), and set
```json
"typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false,

"javascript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces": false,
``` There is also an option for[x]`.

[mentapro]

@aluanhaddad I set these two options to false, but auto-import still inserts spaces. These options do not work.
I use VS Code 1.20.0

[aluanhaddad]

Just format the document after an import is generated.

[ravsom]

@mentapro I had a similar problem and uninstalled some other styling plugins like Prettier. Incidentally, some of the plugins overrides these settings. Unfortunately you have to find it out the hard way by uninstalling plugins and trying again.

[mentapro]

@ravsom It's strange, but now I tried these two settings again and they are working fine. I have plugin Beautify and VSCode 1.23.1. Thanks

[paolobueno]

+1 for getting this issue from an extension in vscode.

esbenp.prettier-vscode replaces vscode's formatting with Prettier transparently, and has the equivalent setting "prettier.bracketSpacing": false.

[daviddongguo]

It works when setting prettier bracketSpacing false

[cawoodm]

Stupid question: why is VSCode doing all this auto-fix stuff if we have ESLint rules which say it shouldn't? Surely there's a fundamental conflict here?

[kukjevov]

@cawoodm One question, do you think everybody is using ESLint? And also do you think that there is only one format of code ;-)?

This is awesome feature :).

[cawoodm]

Hmm... I thought it was a standard - but whatever people use they may see ESLint/TSLint/Whateva highlight code as incorrect which VS Code itself changed to be incorrect. They are fighting each other. If everyone in the team should use the same formatter/prettier then we need this in code (like .eslintrc) and not in everyone's settings.json.

[Xotabu4]

Does someone has fix for this?
In my team some devs are using WebStorm which does not add space in imports, and some devs are using vscode which adds them. This makes a lot of space only changes in pull requests

[mjbvz]

As noted, I believe this is already handled by the typescript.format.insertSpaceAfterOpeningAndBeforeClosingNonemptyBraces setting in VS Code. I also confirmed that auto import respects this option (no format should be required)