You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to use defaultFormatter with biome extention for some TypeScript workspace that has biome. But workspace setting does not override user setting.
The described behavior is how it is expected to work. If you disagree, please explain what is expected and what is not in more detail. See also our issue reporting guidelines.
Oh, So sorry about I've not read the document completely.
However, it's a bit confusing that a high-priority workspace setting is ignored by a low-priority user setting.
It would make sense if "when a high-priority setting (workspace) with multiple languages is found, lower other setting is ignored and not merged," but...
Anyway, I and our teams will use only single language format.
Thank you for your reply despite your busy schedule!
Type: Bug
I'd like to use defaultFormatter with biome extention for some TypeScript workspace that has biome. But workspace setting does not override user setting.
I have user setting like below:
I set workspace setting like below:
If I remove the defaultFormatter line in user setting, vscode uses workspace's setting so those have correct values.
Document said "Language-specific workspace settings" is stronger than "Language-specific user settings": https://code.visualstudio.com/docs/getstarted/settings#_settings-precedence
Thank you.
VS Code version: Code 1.92.2 (fee1edb, 2024-08-14T17:29:30.058Z)
OS version: Windows_NT x64 10.0.19045
Modes:
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
The text was updated successfully, but these errors were encountered: