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
{{ message }}
Repository navigation
Feature request: Support resource scoped settings #722
I rely heavily on vscode's multi-root workspaces feature. However, when using multi-root workspaces I can only change settings for this extension across the entire workspace and not inside individual projects in the workspace.
When I set any of the extension settings inside the .vscode/settings.json file in my project, they're disabled and when I mouse over them I see this message:
This setting cannot be applied in this workspace. It will be applied when you open the containing workspace folder directly.
If I understand correctly, it seems like support has to be added to the extension itself:
You as extension author have to make the decision which scope applies to your settings:
Scope
Description
window
The setting is applied to the entire VS Code instance.
resource
The setting is applied depending on an active resource.
By default, all settings have the window scope, however, we encourage you to support settings on the resource scope. Settings that apply on the window level are not supported once they are defined within a workspace folder, and as soon as the user entered a multi-root workspace. Settings that apply on a resource level however are supported, and as such, each workspace folder can have different values for these settings.
Today LemMinx (our XML language server) doesn't support workspace folder (for settings), but we did that for our another project Quarkus Qute LS. I think it is doable.
Without this support, is there any way to share formatting preferences with a team? Normally I'd put shared settings in .vscode/settings.json, but now everyone has to hand-copy the same settings. Something I'm missing?
Activity
angelozerr commentedon Jun 21, 2022
Today LemMinx (our XML language server) doesn't support workspace folder (for settings), but we did that for our another project Quarkus Qute LS. I think it is doable.
gillibrand commentedon Feb 9, 2023
Without this support, is there any way to share formatting preferences with a team? Normally I'd put shared settings in
.vscode/settings.json, but now everyone has to hand-copy the same settings. Something I'm missing?gian1200 commentedon May 26, 2026
+1
Is there any news? I'd be nice to have "xml.format.maxLineWidth" per project
Support scoped workspace/configuration with scopeUri for per-document
Support scoped workspace/configuration with scopeUri for per-document
Support scoped workspace/configuration with scopeUri for per-document
Support scoped workspace/configuration with scopeUri for per-document
Support scoped workspace/configuration with scopeUri for per-document
angelozerr commentedon Oct 14, 2026
Fixed with eclipse-lemminx/lemminx#1877 but only for
xml.format.*settings.If you need more settings (ex: completion etc) please create a new issue