FR: disable/configure rules in VSC settings.json

[lethefrost]

If biome-vscode could read VSC settings.json to determine the customized rules when linting in VSC editors, it would be greatly appreciated!

[sunneydev]

+1. Biome should be able to be disabled as a whole from settings.json.

[yg-i]

+1.

At the same time, can anyone tell me if it's possible at the moment to set Biome to use {"semicolons": "asNeeded"} in VSCode, by whatever route? With Prettier you can either use settings UI or the settings.json. Is this possible at all for Biome VSCode?

[nemchik]

+1

I keep ending up disabling the biome extension entirely because many projects I work with do not yet use biome (out of my hands) but I would love to be able to still to use the formatter and just not have the linter showing red all over the editor.

The most desirable behavior for me would be "global" settings for the extension that are ignored when a biome config exists within a project. Ex: I might disable linting entirely from a "global" point of view, but when I open a project with a biome config I would want linting enabled.

[SnoepNFTs]

Could anyone confirm whether this is possible yet? it is really annoying to see red all over my code.

[nhedger]

This is currently not possible. The current recommended way is to disable the rules in biome.json.

[colinhacks]

As a +1 I would love the ability to disable Biome in settings.json. I'm currently switching often between a main and next branches of a repo. In next we've already migrated to Biome but in main we're still using prettier. Currently I have to "Enable/Disable in Workspace" every time I switch because there's no way to indicate persistently that I don't want to use Biome in a given project.

[nhedger]

This will be covered by V3. You can track the progress in #201