-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
update rust-analyzer to 2025-02-10 #147
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Following are the settings schema changes between tags --- /dev/fd/63 2025-02-15 22:37:15.362786214 +0000
+++ /dev/fd/62 2025-02-15 22:37:15.362786214 +0000
@@ -22,6 +22,11 @@
"default": true,
"type": "boolean"
},
+ "rust-analyzer.showSyntaxTree": {
+ "markdownDescription": "Whether to show the syntax tree view.",
+ "default": false,
+ "type": "boolean"
+ },
"rust-analyzer.testExplorer": {
"markdownDescription": "Whether to show the test explorer.",
"default": false,
@@ -84,6 +89,11 @@
"$rustc"
],
"markdownDescription": "Problem matchers to use for `rust-analyzer.run` command, eg `[\"$rustc\", \"$rust-panic\"]`."
+ },
+ "rust-analyzer.runnables.askBeforeUpdateTest": {
+ "type": "boolean",
+ "default": true,
+ "markdownDescription": "Ask before updating the test when running it."
}
}
},
@@ -102,6 +112,60 @@
],
"default": "openLogs",
"markdownDescription": "Action to run when clicking the extension status bar item."
+ },
+ "rust-analyzer.statusBar.showStatusBar": {
+ "markdownDescription": "When to show the extension status bar.\n\n`\"always\"` Always show the status bar.\n\n`\"never\"` Never show the status bar.\n\n`{ documentSelector: <DocumentSelector>[] }` Show the status bar if the open file matches any of the given document selectors.\n\nSee [VS Code -- DocumentSelector](https://code.visualstudio.com/api/references/document-selector) for more information.",
+ "anyOf": [
+ {
+ "type": "string",
+ "enum": [
+ "always",
+ "never"
+ ]
+ },
+ {
+ "type": "object",
+ "properties": {
+ "documentSelector": {
+ "type": "array",
+ "items": {
+ "type": "object",
+ "properties": {
+ "language": {
+ "type": "string"
+ },
+ "notebookType": {
+ "type": "string"
+ },
+ "scheme": {
+ "type": "string"
+ },
+ "pattern": {
+ "type": "string"
+ }
+ }
+ }
+ }
+ }
+ }
+ ],
+ "default": {
+ "documentSelector": [
+ {
+ "language": "rust"
+ },
+ {
+ "pattern": "**/Cargo.toml"
+ },
+ {
+ "pattern": "**/Cargo.lock"
+ },
+ {
+ "scheme": "output",
+ "pattern": "extension-output-rust-lang.rust-analyzer*"
+ }
+ ]
+ }
}
}
},
@@ -413,11 +477,14 @@
"properties": {
"rust-analyzer.cargo.cfgs": {
"markdownDescription": "List of cfg options to enable with the given values.",
- "default": {
- "miri": null,
- "debug_assertions": null
- },
- "type": "object"
+ "default": [
+ "debug_assertions",
+ "miri"
+ ],
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
}
}
},
@@ -496,24 +563,6 @@
{
"title": "cargo",
"properties": {
- "rust-analyzer.cargo.sysrootQueryMetadata": {
- "markdownDescription": "How to query metadata for the sysroot crate. Using cargo metadata allows rust-analyzer\nto analyze third-party dependencies of the standard libraries.",
- "default": "cargo_metadata",
- "type": "string",
- "enum": [
- "none",
- "cargo_metadata"
- ],
- "enumDescriptions": [
- "Do not query sysroot metadata, always use stitched sysroot.",
- "Use `cargo metadata` to query sysroot metadata."
- ]
- }
- }
- },
- {
- "title": "cargo",
- "properties": {
"rust-analyzer.cargo.sysrootSrc": {
"markdownDescription": "Relative path to the sysroot library sources. If left unset, this will default to\n`{cargo.sysroot}/lib/rustlib/src/rust/library`.\n\nThis option does not take effect until rust-analyzer is restarted.",
"default": null,
@@ -528,7 +577,7 @@
"title": "cargo",
"properties": {
"rust-analyzer.cargo.target": {
- "markdownDescription": "Compilation target override (target triple).",
+ "markdownDescription": "Compilation target override (target tuple).",
"default": null,
"type": [
"null",
@@ -740,7 +789,7 @@
"title": "check",
"properties": {
"rust-analyzer.check.workspace": {
- "markdownDescription": "Whether `--workspace` should be passed to `cargo check`.\nIf false, `-p <package>` will be passed instead.",
+ "markdownDescription": "Whether `--workspace` should be passed to `cargo check`.\nIf false, `-p <package>` will be passed instead if applicable. In case it is not, no\ncheck will be performed.",
"default": true,
"type": "boolean"
}
@@ -759,6 +808,26 @@
{
"title": "completion",
"properties": {
+ "rust-analyzer.completion.autoAwait.enable": {
+ "markdownDescription": "Toggles the additional completions that automatically show method calls and field accesses with `await` prefixed to them when completing on a future.",
+ "default": true,
+ "type": "boolean"
+ }
+ }
+ },
+ {
+ "title": "completion",
+ "properties": {
+ "rust-analyzer.completion.autoIter.enable": {
+ "markdownDescription": "Toggles the additional completions that automatically show method calls with `iter()` or `into_iter()` prefixed to them when completing on a type that has them.",
+ "default": true,
+ "type": "boolean"
+ }
+ }
+ },
+ {
+ "title": "completion",
+ "properties": {
"rust-analyzer.completion.autoimport.enable": {
"markdownDescription": "Toggles the additional completions that automatically add imports when completed.\nNote that your client must specify the `additionalTextEdits` LSP client capability to truly have this feature enabled.",
"default": true,
@@ -769,6 +838,51 @@
{
"title": "completion",
"properties": {
+ "rust-analyzer.completion.autoimport.exclude": {
+ "markdownDescription": "A list of full paths to items to exclude from auto-importing completions.\n\nTraits in this list won't have their methods suggested in completions unless the trait\nis in scope.\n\nYou can either specify a string path which defaults to type \"always\" or use the more verbose\nform `{ \"path\": \"path::to::item\", type: \"always\" }`.\n\nFor traits the type \"methods\" can be used to only exclude the methods but not the trait itself.\n\nThis setting also inherits `#rust-analyzer.completion.excludeTraits#`.",
+ "default": [
+ {
+ "path": "core::borrow::Borrow",
+ "type": "methods"
+ },
+ {
+ "path": "core::borrow::BorrowMut",
+ "type": "methods"
+ }
+ ],
+ "type": "array",
+ "items": {
+ "anyOf": [
+ {
+ "type": "string"
+ },
+ {
+ "type": "object",
+ "properties": {
+ "path": {
+ "type": "string"
+ },
+ "type": {
+ "type": "string",
+ "enum": [
+ "always",
+ "methods"
+ ],
+ "enumDescriptions": [
+ "Do not show this item or its methods (if it is a trait) in auto-import completions.",
+ "Do not show this traits methods in auto-import completions."
+ ]
+ }
+ }
+ }
+ ]
+ }
+ }
+ }
+ },
+ {
+ "title": "completion",
+ "properties": {
"rust-analyzer.completion.autoself.enable": {
"markdownDescription": "Toggles the additional completions that automatically show method calls and field accesses\nwith `self` prefixed to them when inside a method.",
"default": true,
@@ -799,6 +913,19 @@
{
"title": "completion",
"properties": {
+ "rust-analyzer.completion.excludeTraits": {
+ "markdownDescription": "A list of full paths to traits whose methods to exclude from completion.\n\nMethods from these traits won't be completed, even if the trait is in scope. However, they will still be suggested on expressions whose type is `dyn Trait`, `impl Trait` or `T where T: Trait`.\n\nNote that the trait themselves can still be completed.",
+ "default": [],
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
+ }
+ }
+ },
+ {
+ "title": "completion",
+ "properties": {
"rust-analyzer.completion.fullFunctionSignatures.enable": {
"markdownDescription": "Whether to show full function/method signatures in completion docs.",
"default": false,
@@ -1145,6 +1272,16 @@
{
"title": "hover",
"properties": {
+ "rust-analyzer.hover.actions.updateTest.enable": {
+ "markdownDescription": "Whether to show `Update Test` action. Only applies when\n`#rust-analyzer.hover.actions.enable#` and `#rust-analyzer.hover.actions.run.enable#` are set.",
+ "default": true,
+ "type": "boolean"
+ }
+ }
+ },
+ {
+ "title": "hover",
+ "properties": {
"rust-analyzer.hover.documentation.enable": {
"markdownDescription": "Whether to show documentation on hover.",
"default": true,
@@ -1175,6 +1312,29 @@
{
"title": "hover",
"properties": {
+ "rust-analyzer.hover.maxSubstitutionLength": {
+ "markdownDescription": "Whether to show what types are used as generic arguments in calls etc. on hover, and what is their max length to show such types, beyond it they will be shown with ellipsis.\n\nThis can take three values: `null` means \"unlimited\", the string `\"hide\"` means to not show generic substitutions at all, and a number means to limit them to X characters.\n\nThe default is 20 characters.",
+ "default": 20,
+ "anyOf": [
+ {
+ "type": "null"
+ },
+ {
+ "type": "string",
+ "enum": [
+ "hide"
+ ]
+ },
+ {
+ "type": "integer"
+ }
+ ]
+ }
+ }
+ },
+ {
+ "title": "hover",
+ "properties": {
"rust-analyzer.hover.memoryLayout.alignment": {
"markdownDescription": "How to render the align information in a memory layout hover.",
"default": "hexadecimal",
@@ -1630,6 +1790,16 @@
{
"title": "inlayHints",
"properties": {
+ "rust-analyzer.inlayHints.implicitSizedBoundHints.enable": {
+ "markdownDescription": "Whether to show inlay hints for the implied type parameter `Sized` bound.",
+ "default": false,
+ "type": "boolean"
+ }
+ }
+ },
+ {
+ "title": "inlayHints",
+ "properties": {
"rust-analyzer.inlayHints.lifetimeElisionHints.enable": {
"markdownDescription": "Whether to show inlay type hints for elided lifetimes in function signatures.",
"default": "never",
@@ -1744,6 +1914,16 @@
{
"title": "inlayHints",
"properties": {
+ "rust-analyzer.inlayHints.typeHints.hideClosureParameter": {
+ "markdownDescription": "Whether to hide inlay parameter type hints for closures.",
+ "default": false,
+ "type": "boolean"
+ }
+ }
+ },
+ {
+ "title": "inlayHints",
+ "properties": {
"rust-analyzer.inlayHints.typeHints.hideNamedConstructor": {
"markdownDescription": "Whether to hide inlay type hints for constructors.",
"default": false,
@@ -1900,6 +2080,16 @@
}
},
{
+ "title": "lens",
+ "properties": {
+ "rust-analyzer.lens.updateTest.enable": {
+ "markdownDescription": "Whether to show `Update Test` lens. Only applies when\n`#rust-analyzer.lens.enable#` and `#rust-analyzer.lens.run.enable#` are set.",
+ "default": true,
+ "type": "boolean"
+ }
+ }
+ },
+ {
"title": "general",
"properties": {
"rust-analyzer.linkedProjects": {
@@ -2247,10 +2437,26 @@
{
"title": "typing",
"properties": {
- "rust-analyzer.typing.autoClosingAngleBrackets.enable": {
- "markdownDescription": "Whether to insert closing angle brackets when typing an opening angle bracket of a generic argument list.",
- "default": false,
- "type": "boolean"
+ "rust-analyzer.typing.triggerChars": {
+ "markdownDescription": "Specify the characters allowed to invoke special on typing triggers.\n- typing `=` after `let` tries to smartly add `;` if `=` is followed by an existing expression\n- typing `=` between two expressions adds `;` when in statement position\n- typing `=` to turn an assignment into an equality comparison removes `;` when in expression position\n- typing `.` in a chain method call auto-indents\n- typing `{` or `(` in front of an expression inserts a closing `}` or `)` after the expression\n- typing `{` in a use item adds a closing `}` in the right place\n- typing `>` to complete a return type `->` will insert a whitespace after it\n- typing `<` in a path or type position inserts a closing `>` after the path or type.",
+ "default": "=.",
+ "type": [
+ "null",
+ "string"
+ ]
+ }
+ }
+ },
+ {
+ "title": "vfs",
+ "properties": {
+ "rust-analyzer.vfs.extraIncludes": {
+ "markdownDescription": "Additional paths to include in the VFS. Generally for code that is\ngenerated or otherwise managed by a build system outside of Cargo,\nthough Cargo might be the eventual consumer.",
+ "default": [],
+ "type": "array",
+ "items": {
+ "type": "string"
+ }
}
}
}, |
648d00f
to
fe282d6
Compare
b7be946
to
1f87462
Compare
1f87462
to
adca5bb
Compare
adca5bb
to
8ebeee7
Compare
8ebeee7
to
1e34a12
Compare
1e34a12
to
2afb4cb
Compare
2afb4cb
to
0539526
Compare
0539526
to
98a3d28
Compare
98a3d28
to
cf15b0b
Compare
cf15b0b
to
6438572
Compare
6438572
to
e9484f4
Compare
e9484f4
to
269855e
Compare
The following settings will be commented out because they are not supported in ST: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Update rust-analyzer from 2024-12-02 to 2025-02-10 (see all changes).