Merge branch 'main' into rename-ruff_lsp-to-ruff

Author: okuuva

schemas/basedpyright.json

@@ -40,7 +40,7 @@
       "type": "string"
     },
     "basedpyright.analysis.diagnosticSeverityOverrides": {
-      "description": "Allows a user to override the severity levels for individual diagnostics. Use the rule name as a key and one of \"error\", \"warning\", \"information\", \"none\", `true` (alias for \"error\") or `false` (alias for \"none\") as value. The default value shown for each diagnostic is the default when \"basedpyright.analysis.typeCheckingMode\" is set to \"standard\". See [here](https://github.com/detachhead/basedpyright/blob/main/docs/configuration.md#diagnostic-rule-defaults) for defaults for each type checking mode (\"off\", \"basic\", \"standard\", \"strict\", and \"all\").",
+      "markdownDescription": "Allows a user to override the severity levels for individual diagnostics. Use the rule name as a key and one of \"error\", \"warning\", \"information\", \"none\", `true` (alias for \"error\") or `false` (alias for \"none\") as value. The default value shown for each diagnostic is the default when \"basedpyright.analysis.typeCheckingMode\" is set to \"standard\". See [here](https://docs.basedpyright.com/latest/configuration/config-files/#diagnostic-settings-defaults) for defaults for each type checking mode (\"off\", \"basic\", \"standard\", \"strict\", and \"all\").",
       "properties": {
         "reportAbstractUsage": {
           "default": "error",

schemas/dartls.json

@@ -223,6 +223,15 @@
       "scope": "resource",
       "type": "boolean"
     },
+    "dart.coverageExcludePatterns": {
+      "default": [],
+      "items": {
+        "type": "string"
+      },
+      "markdownDescription": "An array of glob patterns to exclude from code coverage results. Paths matching any of these patterns will still be collected by the Dart VM but not be included in coverage reported to VS Code.",
+      "scope": "window",
+      "type": "array"
+    },
     "dart.customDartDapPath": {
       "default": null,
       "description": "The path to a custom Dart Debug Adapter. This setting is intended for use by Dart Debug Adapter developers. Use `~` to insert the user's home directory (the path should then use `/` separators even on Windows).",
@@ -577,6 +586,26 @@
       "scope": "window",
       "type": "boolean"
     },
+    "dart.experimentalFlutterWidgetPreview": {
+      "default": false,
+      "markdownDescription": "EXPERIMENTAL: Whether to enable the Flutter Widget Preview experimental feature. This feature requires an unreleased version of Flutter from the `master` branch.",
+      "scope": "window",
+      "type": "boolean"
+    },
+    "dart.experimentalFlutterWidgetPreviewLocation": {
+      "default": "sidebar",
+      "enum": [
+        "beside",
+        "sidebar"
+      ],
+      "enumDescriptions": [
+        "Open the Flutter Widget Preview beside the active editor",
+        "Open the Flutter Widget Preview in the sidebar"
+      ],
+      "markdownDescription": "Where to display the Flutter Widget Preview.",
+      "scope": "window",
+      "type": "string"
+    },
     "dart.experimentalRefactors": {
       "default": false,
       "markdownDescription": "Whether to enable experimental (possibly unfinished or unstable) refactors on the lightbulb menu. This setting is intended for use by Dart Analysis Server developers or users that want to try out and provide feedback on in-progress refactors.",
@@ -864,6 +893,15 @@
       "markdownDescription": "Sets the [Web renderer](https://flutter.dev/to/web-renderers) used for Flutter web apps.",
       "scope": "window"
     },
+    "dart.flutterWidgetPreviewLogFile": {
+      "default": null,
+      "markdownDescription": "The path to a log file for the `flutter widget-preview` service. Use `${workspaceName}` to insert the name of the current workspace in the file path. Use `~` to insert the user's home directory (the path should then use `/` separators even on Windows). Only the noted substitutions are supported, others will stay as-is.",
+      "scope": "machine-overridable",
+      "type": [
+        "null",
+        "string"
+      ]
+    },
     "dart.getDartSdkCommand": {
       "additionalProperties": false,
       "default": null,
@@ -1046,6 +1084,17 @@
         "string"
       ]
     },
+    "dart.mcpServerTools": {
+      "additionalProperties": {
+        "type": "boolean"
+      },
+      "default": {
+        "run_tests": false
+      },
+      "markdownDescription": "A map of MCP tool names to booleans to enable/disable specific tools from the Dart MCP server. Tools set to `false` will be excluded (if supported). By default, tools that overlap with built-in VS Code functionality will be excluded.",
+      "scope": "window",
+      "type": "object"
+    },
     "dart.normalizeFileCasing": {
       "default": false,
       "description": "Whether to normalize file casings before sending them to the LSP server. This may fix issues with file_names lints not disappearing after renaming a file if the VS Code API continues to use the original casing.",
@@ -1066,7 +1115,7 @@
     },
     "dart.onlyAnalyzeProjectsWithOpenFiles": {
       "default": false,
-      "description": "Whether to ignore workspace folders and perform analysis based on the open files, as if no workspace was open at all. This allows opening large folders without causing them to be completely analyzed.",
+      "description": "Whether to ignore workspace folders and perform analysis based on the open files, as if no workspace was open at all. This allows opening very large folders without causing them to be fully analyzed but will result a lot of re-analysis as files are opened/closed. This is **not** recommended for small or medium sized workspaces, only very large workspaces where you are working in only a small part.",
       "scope": "window",
       "type": "boolean"
     },
@@ -1364,6 +1413,12 @@
       "scope": "window",
       "type": "boolean"
     },
+    "dart.useFlutterDev": {
+      "default": false,
+      "description": "Whether to use `flutter-dev` instead of `flutter`. This is a script for developers of the `flutter` tool to run from source and will run more slowly than the compiled tool.",
+      "scope": "window",
+      "type": "boolean"
+    },
     "dart.useLegacyDebugAdapters": {
       "default": null,
       "markdownDescription": "**LEGACY SETTING: Legacy debug adapters are not recommended since Dart v3.4.**\n\nWhether to use the legacy debug adapters even if the new debug adapters are available in the current Dart/Flutter SDKs contain. Setting the value to `true` will force use of the legacay adapters. Setting to `false` will force use of the SDK adapters. Leaving as `null` will allow the extension to decide which debug adapters to use depending on the SDK version and rollout progress.",

schemas/elixirls.json

@@ -84,6 +84,12 @@
       "type": "array",
       "uniqueItems": true
     },
+    "elixirLS.dotFormatter": {
+      "description": "Path to a custom .formatter.exs file used when formatting documents",
+      "minLength": 0,
+      "scope": "resource",
+      "type": "string"
+    },
     "elixirLS.enableTestLenses": {
       "default": false,
       "description": "Show code lenses to run tests in terminal.",
@@ -114,6 +120,18 @@
       "scope": "resource",
       "type": "string"
     },
+    "elixirLS.mcpEnabled": {
+      "default": false,
+      "description": "Enable or disable the MCP server",
+      "scope": "resource",
+      "type": "boolean"
+    },
+    "elixirLS.mcpPort": {
+      "default": 0,
+      "description": "Set a specific port for the MCP server. If not set, uses `3789 + hash(workspace_path)` for predictable port assignment per workspace",
+      "scope": "resource",
+      "type": "integer"
+    },
     "elixirLS.mixEnv": {
       "default": "test",
       "description": "Mix environment to use for compilation",

schemas/eslint.json

@@ -250,7 +250,10 @@
         "vue",
         "markdown",
         "json",
-        "jsonc"
+        "jsonc",
+        "css",
+        "glimmer-js",
+        "glimmer-ts"
       ],
       "description": "An array of language ids for which the extension should probe if support is installed.",
       "items": {

schemas/hie.json

@@ -161,6 +161,18 @@
       "scope": "resource",
       "type": "boolean"
     },
+    "haskell.plugin.eval.codeActionsOn": {
+      "default": true,
+      "description": "Enables eval code actions",
+      "scope": "resource",
+      "type": "boolean"
+    },
+    "haskell.plugin.eval.codeLensOn": {
+      "default": true,
+      "description": "Enables eval code lenses",
+      "scope": "resource",
+      "type": "boolean"
+    },
     "haskell.plugin.eval.config.diff": {
       "default": true,
       "markdownDescription": "Enable the diff output (WAS/NOW) of eval lenses",
@@ -173,12 +185,6 @@
       "scope": "resource",
       "type": "boolean"
     },
-    "haskell.plugin.eval.globalOn": {
-      "default": true,
-      "description": "Enables eval plugin",
-      "scope": "resource",
-      "type": "boolean"
-    },
     "haskell.plugin.explicit-fields.codeActionsOn": {
       "default": true,
       "description": "Enables explicit-fields code actions",

schemas/julials.json

@@ -222,6 +222,12 @@
       "scope": "machine-overridable",
       "type": "string"
     },
+    "julia.languageServerJuliaupChannel": {
+      "default": "release",
+      "description": "Juliaup channel to use for the language server (e.g., 'release', 'lts', 'beta'). Can be overridden by JULIA_VSCODE_LANGUAGESERVER_CHANNEL environment variable.",
+      "scope": "machine-overridable",
+      "type": "string"
+    },
     "julia.lint.call": {
       "default": true,
       "description": "This compares call signatures against all known methods for the called function. Calls with too many or too few arguments, or unknown keyword parameters are highlighted.",

schemas/omnisharp.json

@@ -987,7 +987,7 @@
       "type": "boolean"
     },
     "razor.languageServer.cohostingEnabled": {
-      "default": false,
+      "default": true,
       "description": "%configuration.razor.languageServer.cohostingEnabled%",
       "tags": [
         "experimental"

schemas/perlnavigator.json

@@ -72,6 +72,12 @@
       "scope": "resource",
       "type": "string"
     },
+    "perlnavigator.perlcriticMessageFormat": {
+      "default": "%m",
+      "description": "Format for Perl::Critic messages. Use %e to include policy explanations",
+      "scope": "resource",
+      "type": "string"
+    },
     "perlnavigator.perlcriticProfile": {
       "default": "",
       "description": "Path to perl critic profile. Otherwise perlcritic itself will default to ~/.perlcriticrc. (no aliases, .bat files or ~/)",

schemas/rescriptls.json

@@ -26,6 +26,11 @@
       "description": "Enable (experimental) code lens for function definitions.",
       "type": "boolean"
     },
+    "rescript.settings.compileStatus.enable": {
+      "default": true,
+      "description": "Show compile status in the status bar (compiling/errors/warnings/success).",
+      "type": "boolean"
+    },
     "rescript.settings.incrementalTypechecking.acrossFiles": {
       "default": false,
       "description": "(beta/experimental) Enable incremental type checking across files, so that unsaved file A gets access to unsaved file B.",

schemas/rust_analyzer.json

@@ -96,7 +96,7 @@
       "items": {
         "type": "string"
       },
-      "markdownDescription": "Override the command rust-analyzer uses to run build scripts and\nbuild procedural macros. The command is required to output json\nand should therefore include `--message-format=json` or a similar\noption.\n\nIf there are multiple linked projects/workspaces, this command is invoked for\neach of them, with the working directory being the workspace root\n(i.e., the folder containing the `Cargo.toml`). This can be overwritten\nby changing `#rust-analyzer.cargo.buildScripts.invocationStrategy#`.\n\nBy default, a cargo invocation will be constructed for the configured\ntargets and features, with the following base command line:\n\n```bash\ncargo check --quiet --workspace --message-format=json --all-targets --keep-going\n```\n.",
+      "markdownDescription": "Override the command rust-analyzer uses to run build scripts and\nbuild procedural macros. The command is required to output json\nand should therefore include `--message-format=json` or a similar\noption.\n\nIf there are multiple linked projects/workspaces, this command is invoked for\neach of them, with the working directory being the workspace root\n(i.e., the folder containing the `Cargo.toml`). This can be overwritten\nby changing `#rust-analyzer.cargo.buildScripts.invocationStrategy#`.\n\nBy default, a cargo invocation will be constructed for the configured\ntargets and features, with the following base command line:\n\n```bash\ncargo check --quiet --workspace --message-format=json --all-targets --keep-going\n```\n\nNote: The option must be specified as an array of command line arguments, with\nthe first argument being the name of the command to run.",
       "type": [
         "null",
         "array"
@@ -296,7 +296,7 @@
       "items": {
         "type": "string"
       },
-      "markdownDescription": "Override the command rust-analyzer uses instead of `cargo check` for\ndiagnostics on save. The command is required to output json and\nshould therefore include `--message-format=json` or a similar option\n(if your client supports the `colorDiagnosticOutput` experimental\ncapability, you can use `--message-format=json-diagnostic-rendered-ansi`).\n\nIf you're changing this because you're using some tool wrapping\nCargo, you might also want to change\n`#rust-analyzer.cargo.buildScripts.overrideCommand#`.\n\nIf there are multiple linked projects/workspaces, this command is invoked for\neach of them, with the working directory being the workspace root\n(i.e., the folder containing the `Cargo.toml`). This can be overwritten\nby changing `#rust-analyzer.check.invocationStrategy#`.\n\nIf `$saved_file` is part of the command, rust-analyzer will pass\nthe absolute path of the saved file to the provided command. This is\nintended to be used with non-Cargo build systems.\nNote that `$saved_file` is experimental and may be removed in the future.\n\nAn example command would be:\n\n```bash\ncargo check --workspace --message-format=json --all-targets\n```\n.",
+      "markdownDescription": "Override the command rust-analyzer uses instead of `cargo check` for\ndiagnostics on save. The command is required to output json and\nshould therefore include `--message-format=json` or a similar option\n(if your client supports the `colorDiagnosticOutput` experimental\ncapability, you can use `--message-format=json-diagnostic-rendered-ansi`).\n\nIf you're changing this because you're using some tool wrapping\nCargo, you might also want to change\n`#rust-analyzer.cargo.buildScripts.overrideCommand#`.\n\nIf there are multiple linked projects/workspaces, this command is invoked for\neach of them, with the working directory being the workspace root\n(i.e., the folder containing the `Cargo.toml`). This can be overwritten\nby changing `#rust-analyzer.check.invocationStrategy#`.\n\nIf `$saved_file` is part of the command, rust-analyzer will pass\nthe absolute path of the saved file to the provided command. This is\nintended to be used with non-Cargo build systems.\nNote that `$saved_file` is experimental and may be removed in the future.\n\nAn example command would be:\n\n```bash\ncargo check --workspace --message-format=json --all-targets\n```\n\nNote: The option must be specified as an array of command line arguments, with\nthe first argument being the name of the command to run.",
       "type": [
         "null",
         "array"
@@ -598,6 +598,11 @@
       "markdownDescription": "List of warnings that should be displayed with info severity.\n\nThe warnings will be indicated by a blue squiggly underline in code and a blue icon in\nthe `Problems Panel`.",
       "type": "array"
     },
+    "rust-analyzer.document.symbol.search.excludeLocals": {
+      "default": true,
+      "markdownDescription": "Exclude all locals from document symbol search.",
+      "type": "boolean"
+    },
     "rust-analyzer.files.exclude": {
       "default": [],
       "items": {
@@ -992,6 +997,11 @@
       "markdownDescription": "Show enum variant discriminant hints.",
       "type": "string"
     },
+    "rust-analyzer.inlayHints.expressionAdjustmentHints.disableReborrows": {
+      "default": true,
+      "markdownDescription": "Disable reborrows in expression adjustments inlay hints.\n\nReborrows are a pair of a builtin deref then borrow, i.e. `&*`. They are inserted by the compiler but are mostly useless to the programmer.\n\nNote: if the deref is not builtin (an overloaded deref), or the borrow is `&raw const`/`&raw mut`, they are not removed.",
+      "type": "boolean"
+    },
     "rust-analyzer.inlayHints.expressionAdjustmentHints.enable": {
       "default": "never",
       "enum": [
@@ -1410,7 +1420,7 @@
       "items": {
         "type": "string"
       },
-      "markdownDescription": "Advanced option, fully override the command rust-analyzer uses for\nformatting. This should be the equivalent of `rustfmt` here, and\nnot that of `cargo fmt`. The file contents will be passed on the\nstandard input and the formatted result will be read from the\nstandard output.",
+      "markdownDescription": "Advanced option, fully override the command rust-analyzer uses for\nformatting. This should be the equivalent of `rustfmt` here, and\nnot that of `cargo fmt`. The file contents will be passed on the\nstandard input and the formatted result will be read from the\nstandard output.\n\nNote: The option must be specified as an array of command line arguments, with\nthe first argument being the name of the command to run.",
       "type": [
         "null",
         "array"