FR: disable/configure rules in VSC settings.json #97
Replies: 5 comments 3 replies
-
+1. Biome should be able to be disabled as a whole from |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
+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. |
Beta Was this translation helpful? Give feedback.
-
Could anyone confirm whether this is possible yet? it is really annoying to see red all over my code. |
Beta Was this translation helpful? Give feedback.
-
There is this global settings for user settings.json but it doesn’t work. I’d like to have a global configuration fallback that could apply to any files opened in VSCode and not only those inside project with a biome.json. And in project, an init command in palette would be helpful as mentioned at #230. By the way, I have |
Beta Was this translation helpful? Give feedback.
-
If biome-vscode could read VSC
settings.json
to determine the customized rules when linting in VSC editors, it would be greatly appreciated!Beta Was this translation helpful? Give feedback.
All reactions