diff --git a/schemas/hie.json b/schemas/hie.json index cb1ccf3..e5de48e 100644 --- a/schemas/hie.json +++ b/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", diff --git a/schemas/rust_analyzer.json b/schemas/rust_analyzer.json index 53f4675..90855e0 100644 --- a/schemas/rust_analyzer.json +++ 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" @@ -1410,7 +1410,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" diff --git a/types/lsp.lua b/types/lsp.lua index 150047a..8c26c4d 100644 --- a/types/lsp.lua +++ b/types/lsp.lua @@ -4557,13 +4557,19 @@ ---@field exception boolean ---@class _.lspconfig.settings.hie.Eval ----@field config _.lspconfig.settings.hie.Config --- Enables eval plugin +-- Enables eval code actions -- -- ```lua -- default = true -- ``` ----@field globalOn boolean +---@field codeActionsOn boolean +-- Enables eval code lenses +-- +-- ```lua +-- default = true +-- ``` +---@field codeLensOn boolean +---@field config _.lspconfig.settings.hie.Config ---@class _.lspconfig.settings.hie.Explicit-fields -- Enables explicit-fields code actions @@ -13410,7 +13416,9 @@ -- ```bash -- cargo check --quiet --workspace --message-format=json --all-targets --keep-going -- ``` --- . +-- +-- Note: The option must be specified as an array of command line arguments, with +-- the first argument being the name of the command to run. ---@field overrideCommand string[] -- Rerun proc-macros building/build-scripts running when proc-macro -- or build-script sources change and are saved. @@ -13586,7 +13594,9 @@ -- ```bash -- cargo check --workspace --message-format=json --all-targets -- ``` --- . +-- +-- Note: The option must be specified as an array of command line arguments, with +-- the first argument being the name of the command to run. ---@field overrideCommand string[] -- Check for specific targets. Defaults to `#rust-analyzer.cargo.target#` if empty. -- @@ -14557,6 +14567,9 @@ -- not that of `cargo fmt`. The file contents will be passed on the -- standard input and the formatted result will be read from the -- standard output. +-- +-- Note: The option must be specified as an array of command line arguments, with +-- the first argument being the name of the command to run. ---@field overrideCommand string[] ---@field rangeFormatting _.lspconfig.settings.rust_analyzer.RangeFormatting