settings-precedence

VS Code settings precedence dictates that Workspace folder settings override Workspace, User, and Default settings. Your extension must inspect configurations correctly using the appropriate scope to prevent unexpected overrides.

Use the VS Code API inspect() method instead of get() to read configuration values. This allows you to check user-explicit settings at specific scopes before applying updates, preventing accidental overwrites.

The precedence order from highest to lowest is Workspace folder, Workspace, User, and Default. Understanding this hierarchy ensures your extension applies configurations reliably without corrupting user preferences.

Pass the correct scope to getConfiguration() when handling multi-root workspaces. This ensures your extension reads and updates configurations at the appropriate workspace folder level, preventing configuration corruption.

Yes, your extension must inspect all configuration scopes before updating. Failing to check higher-priority scopes like Workspace folder or User settings can result in overwriting explicit user preferences.

The get() method returns the merged configuration value, which may not reflect user-explicit settings. Use inspect() to retrieve the specific values at each scope and determine the actual applied configuration.