Research VS Code settings export/import

a24vinla commented

2026-04-01 12:17:03 +00:00

Collaborator

There should be a way to export/import VS Code settings to allow for coding conventions to be "automatically" followed for each language. This could also be solved with VS Code Extensions for each language, might be simpler.

Related Issue: #51

There should be a way to export/import VS Code settings to allow for coding conventions to be "automatically" followed for each language. This could also be solved with VS Code Extensions for each language, might be simpler. Related Issue: https://git.webug.se/Andras/BoundlessFlowCampus2K/issues/51

a24vinla added the

research

label

2026-04-01 12:36:13 +00:00

b24idalu was assigned by c24elipe

2026-04-02 09:51:09 +00:00

b24idalu commented

2026-04-02 10:29:55 +00:00

Collaborator

One can add specific settings for different languages by going to settings in vscode and searching @lang:{language}, or simply edit general settings. The settings will be written in settings.json that exist here:

Windows %APPDATA%\Code\User\settings.json
macOS $HOME/Library/Application\ Support/Code/User/settings.json
Linux $HOME/.config/Code/User/settings.json

and to share extensions, one can copy the extension folder located here (or making a list somewhere, like the wiki, with extensions to get):

Windows %USERPROFILE%.vscode\extensions
macOS ~/.vscode/extensions
Linux ~/.vscode/extensions

One can add specific settings for different languages by going to settings in vscode and searching @lang:{language}, or simply edit general settings. The settings will be written in settings.json that exist here: - Windows %APPDATA%\Code\User\settings.json - macOS $HOME/Library/Application\ Support/Code/User/settings.json - Linux $HOME/.config/Code/User/settings.json and to share extensions, one can copy the extension folder located here (or making a list somewhere, like the wiki, with extensions to get): - Windows %USERPROFILE%\.vscode\extensions - macOS ~/.vscode/extensions - Linux ~/.vscode/extensions

b24idalu commented

2026-04-02 11:04:52 +00:00

Collaborator

For less work (what Andras mentioned);

"Prettier - Code formatter" (an extension: works with for example: JavaScript, JSON, CSS, HTML. On Pretty.io there exists plugins with sql)
"ESlint" (an extension: works with JavaScript)
EditConfig (which is like settings but project only, is an extension. Works on all languages (i think) (it is based on file extension). Their webpage with examples: EditorConfig)
Artistic (can be retrieved from git, works with: C, C++, C# and Java)

For less work (what Andras mentioned); - "Prettier - Code formatter" (an extension: works with for example: JavaScript, JSON, CSS, HTML. On Pretty.io there exists plugins with sql) - "ESlint" (an extension: works with JavaScript) - EditConfig (which is like settings but project only, is an extension. Works on all languages (i think) (it is based on file extension). Their webpage with examples: [EditorConfig](https://editorconfig.org)) - Artistic (can be retrieved from git, works with: C, C++, C# and Java)

b24idalu added the

needs review

label

2026-04-02 12:31:10 +00:00

b25marem was assigned by c24elipe

2026-04-07 07:40:24 +00:00

a24vinla commented

2026-04-07 07:45:48 +00:00

Author

Collaborator

Looks really good, Prettier seems to be the most used. Could you look into a smart way to share Prettier configs?

b24idalu commented

2026-04-07 08:29:08 +00:00

Collaborator

There exists file that one can add to a project; https://prettier.io/docs/configuration.html that changes the way it is formatted. From what I have found it works on all levels (not only in root). Editorconfig also works with prettier and could also be used but then it has to be read from root.

Also a useful vs setting I found during research is "format on save" that formats the code when saving the file.

There exists file that one can add to a project; [https://prettier.io/docs/configuration.html](configs) that changes the way it is formatted. From what I have found it works on all levels (not only in root). Editorconfig also works with prettier and could also be used but then it has to be read from root. Also a useful vs setting I found during research is "format on save" that formats the code when saving the file.

b25marem commented

2026-04-07 09:20:14 +00:00

Collaborator

Look good. The research covers both VS Code settngs and extensions. I agree that using project-level configuration is better than relying on exporting/importing personal setting. Prettier seems like the best option for sharing formatting rules across the team, and EditorConfig also looks useful as a complement. Maby the only thing missing is a clearer final recommendation for what we actually want to use in the project for exemple, adding a prettier config file yo the repositry.

a24vinla commented

2026-04-07 10:50:33 +00:00

Author

Collaborator

After having talked with the other team leaders we have decided to use Prettier for all languages except C#, which is not inherently supported by prettier, that will use MS-dot.net default. Well done!

a24vinla closed this issue

2026-04-07 10:50:33 +00:00

a24vinla referenced this issue

2026-04-07 11:03:39 +00:00

Create support for Prettier Formatting extension #153

Rows
Columns

Research VS Code settings export/import #79