feat: add workspace initialization command

[AlemTuzlak]

Summary

Added a command that allows you to initalize biome settings in the workspace based on this tweet: https://x.com/colinhacks/status/1841219884287737886 and this dicussion: https://github.com/biomejs/biome-vscode/discussions/230

Description

when you right click on either setttings.json in .vscode or biome.json you can click on the biome: initalize workspace command to add all the required fields into settings.json for biome to work properly, also check this tweet for the merging of the config files: https://x.com/andhaveaniceday/status/1841226098706956625

Feel free to edit and add whatever you deem is needed here

Checklist

• [ ] I have tested my changes on the following platforms:
  • [x] Windows
  • [ ] Linux
  • [ ] macOS

[nhedger]

Thanks for the contrib.

How does that behave when in a a multi-root workspace ?

[AlemTuzlak]

@nhedger seems to get added to test.code-workspace instead of settings.json in the individual ones, what would be the right behaviour here?

[nhedger]

@nhedger seems to get added to test.code-workspace instead of settings.json in the individual ones, what would be the right behaviour here?

I think we'd want the config to be added to the .vscode/settings.json file if the action was triggered from the context menu on that file. Maybe we could also add a context menu for the .code-workspace file, WDYT?

[AlemTuzlak]

@nhedger when you click on the .code-workspace it will generate it on the root of that workspace into a separate .vscode folder, and if you click on the workspaces inside it will generate it there, would that be the expected behavior?

[nhedger]

I would expect it to add the config inside the .code-workspace file in the settings section.

[AlemTuzlak]

@nhedger I can't get it to output it to the .code-workspace file at all, seems that vscode isn't happy with that, when i scope it to the .code-workspace file it's still output to the .vscode folder and whatever I do it's the same result, the only way to allow it on .code-workspace is to manually parse the file and rewrite it with fs it seems, unless I'm missing something.

[AlemTuzlak]

my findings: workspace1/.vscode/settings => if you set output to Workspace it's output to the .code-workspace workspace1/.vscode/settings => if you set output to WorkspaceFolder AND scope it to the current path its output properly (what this PR does) .code-workspace => no scope / scoped to workspace path with Workspace is output to .vscode folder neighbouring it. .code-workspace => no scope / scoped to workspace path with WorkspaceFolder nothing happens .code-workspace => no scope / scoped to workspace path with Global it's output to global settings above the workspace

[AlemTuzlak]

you can easily check if it's a .code-workspace by checking if the args.path ends with that extension and feel free to try it out yourself and see if i've missed something obvious. From my perspective the PR is ready as is, but that feature can be added on top of course!

[colinhacks]

Thanks Alem, I love this!

I do have a question for the maintainers. Why are the per-language settings necessary in the first place? If Biome is set as the top-level default formatter in a workspace, it seems surprising that is isn't used by default for all file types that Biome is capable of formatting. I'm sure this was an intentional decision, but I'd love to see it revisited, especially as Biome matures (and with a new major of the extension on the horizon).

If Biome adds support for additional file types down the line, those will need to be added. This is likely to cause confusion for users who have run the "Biome: Initialize" and assumed Biome will just work moving forward. (On the flip side of this coin, it's probably not a good idea to override the official Svelte/Vue/Astro extensions yet, see my comment in the review interface.)

[ematipico]

I do have a question for the maintainers. Why are the per-language settings necessary in the first place? If Biome is set as the top-level default formatter in a workspace, it seems surprising that is isn't used by default for all file types that Biome is capable of formattin

It isn't necessary, actually. For example, I use the following setting on my VSCode:

{
    "editor.defaultFormatter": "biomejs.biome",
    "editor.formatOnSave": true,
}

These settings work as expected. If they don't, there's probably a bug lurking somewhere (either the extension or the editor).

I suppose the docs are outdated, and at that time, we suggested an opt-in approach not to disrupt the user's settings and default formatter. We are happy to revisit them if you think it's more valuable. There's an open PR for the upcoming v3 of the extension if you're interested: https://github.com/biomejs/website/pull/974

[AlemTuzlak]

@ematipico I also believe there is a bug somewhere, we have been extensively using biome in our company and we had to play around with the settings.json a lot to get it working properly with biome.

I've added the suggested changes by @colinhacks to the PR

[AlemTuzlak]

Hey guys, any updates on this, anything on my side I need to do? Really interested if it will be merged or not!

[nhedger]

Hey @AlemTuzlak, haven't had a chance to test it out yet. I've been taking a break. I'll try to review and test it this week.

[AlemTuzlak]

@nhedger no worries, just wanted to confirm I'm not the cause of it. Great to hear, take your time