Mirrors/rust-analyzer
2
0
Fork 0
mirror of https://github.com/rust-lang/rust-analyzer synced 2024-12-26 13:03:31 +00:00
Code Issues Projects Releases Packages Wiki Activity
rust-analyzer/editors/code/package.json

1402 lines
60 KiB
JSON
Raw Normal View History

JS plugin
2018-07-30 18:58:49 +00:00
{
Rename VS Code extension to rust-analyzer
2020-01-08 16:21:18 +00:00
"name": "rust-analyzer",
"displayName": "rust-analyzer",
Run npm update and add private and preview flags Private stops npm publish working, which would be nonsensical anyway In case it gets added to the vscode extension repository, preview marks it as such Private may also prevent publishing to the vscode extension repository
2018-12-08 20:56:31 +00:00
"description": "An alternative rust language server to the RLS",
"preview": true,
"private": true,
Rename VS Code extension to rust-analyzer
2020-01-08 16:21:18 +00:00
"icon": "icon.png",
Simplify extension tag sniffing
2020-03-19 08:32:57 +00:00
"version": "0.4.0-dev",
Make from-source install use cargo installed binary by default
2020-03-20 11:50:50 +00:00
"releaseTag": null,
you better run
2018-08-27 19:52:43 +00:00
"publisher": "matklad",
"repository": {
fix repo link in package.json
2020-02-02 10:16:41 +00:00
"url": "https://github.com/rust-analyzer/rust-analyzer.git",
"type": "git"
you better run
2018-08-27 19:52:43 +00:00
},
Minimal viable meta
2020-03-02 13:27:26 +00:00
"homepage": "https://rust-analyzer.github.io/",
"license": "MIT OR Apache-2.0",
"keywords": [
"rust"
],
you better run
2018-08-27 19:52:43 +00:00
"categories": [
Minimal viable meta
2020-03-02 13:27:26 +00:00
"Programming Languages"
reorganize
2018-08-10 22:04:09 +00:00
],
you better run
2018-08-27 19:52:43 +00:00
"engines": {
Update vscode
2021-07-10 15:31:42 +00:00
"vscode": "^1.57.0"
you better run
2018-08-27 19:52:43 +00:00
},
Enable SemanticTokens on the client This will crash the extension on stable and insiders without the "--enable-proposed-api matklad.rust-analyzer" command line switch.
2020-02-26 13:42:26 +00:00
"enableProposedApi": true,
you better run
2018-08-27 19:52:43 +00:00
"scripts": {
vscode extension: use esbuild instead of rollup.
2021-08-10 06:56:34 +00:00
"vscode:prepublish": "npm run build-base -- --minify",
Fix extension name
2020-02-17 14:33:31 +00:00
"package": "vsce package -o rust-analyzer.vsix",
Set esbuild target as node14
2021-08-28 14:10:35 +00:00
"build-base": "esbuild ./src/main.ts --bundle --outfile=out/main.js --external:vscode --format=cjs --platform=node --target=node14",
vscode extension: use esbuild instead of rollup.
2021-08-10 06:56:34 +00:00
"build": "npm run build-base -- --sourcemap",
"watch": "npm run build-base -- --sourcemap --watch",
vscode client side tests
2020-05-20 18:03:49 +00:00
"lint": "tsfmt --verify && eslint -c .eslintrc.js --ext ts ./src ./tests",
"fix": " tsfmt -r && eslint -c .eslintrc.js --ext ts ./src ./tests --fix",
Try to fix Code tests
2021-12-01 10:22:34 +00:00
"pretest": "tsc && npm run build",
vscode client side tests
2020-05-20 18:03:49 +00:00
"test": "node ./out/tests/runTests.js"
you better run
2018-08-27 19:52:43 +00:00
},
"dependencies": {
Make extension respect http proxy settings
2021-03-07 09:55:43 +00:00
"https-proxy-agent": "^5.0.0",
Bump node-fetch from 2.6.0 to 2.6.1 in /editors/code Bumps [node-fetch](https://github.com/bitinn/node-fetch) from 2.6.0 to 2.6.1. - [Release notes](https://github.com/bitinn/node-fetch/releases) - [Changelog](https://github.com/node-fetch/node-fetch/blob/master/docs/CHANGELOG.md) - [Commits](https://github.com/bitinn/node-fetch/compare/v2.6.0...v2.6.1) Signed-off-by: dependabot[bot] <support@github.com>
2020-09-12 14:50:54 +00:00
"node-fetch": "^2.6.1",
Bump npm non-dev deps
2021-10-02 04:37:51 +00:00
"vscode-languageclient": "8.0.0-next.2",
"d3": "^7.1.0",
Use d3-graphviz for rendering crates graph on the extension side
2021-08-10 13:34:30 +00:00
"d3-graphviz": "^4.0.0"
you better run
2018-08-27 19:52:43 +00:00
},
"devDependencies": {
Update @types/node
2021-07-10 15:31:33 +00:00
"@types/node": "~14.17.5",
Update @types/node-fetch
2021-07-10 15:28:32 +00:00
"@types/node-fetch": "^2.5.11",
Update vscode
2021-07-10 15:31:42 +00:00
"@types/vscode": "^1.57.0",
Update eslint
2021-07-10 15:34:48 +00:00
"@typescript-eslint/eslint-plugin": "^4.28.2",
"@typescript-eslint/parser": "^4.28.2",
vscode extension: use esbuild instead of rollup.
2021-08-10 06:56:34 +00:00
"esbuild": "^0.12.19",
Update eslint
2021-07-10 15:34:48 +00:00
"eslint": "^7.30.0",
Update tslib
2021-07-10 15:26:06 +00:00
"tslib": "^2.3.0",
Update typescript
2021-07-10 15:25:53 +00:00
"typescript": "^4.3.5",
added fetchLatestArtifactMetadata() and downloadFile() functions
2020-02-07 01:11:24 +00:00
"typescript-formatter": "^7.2.2",
Update vsce
2021-07-10 15:32:31 +00:00
"vsce": "^1.95.1",
Update our vscode npm packages
2021-02-23 16:39:19 +00:00
"vscode-test": "^1.5.1"
Add prettier
2019-12-30 14:08:38 +00:00
},
you better run
2018-08-27 19:52:43 +00:00
"activationEvents": [
Start the extension when rust-analyzer status is run
2019-01-29 17:08:02 +00:00
"onLanguage:rust",
"onCommand:rust-analyzer.analyzerStatus",
Add a command to compute memory usage statistics
2020-07-07 10:10:14 +00:00
"onCommand:rust-analyzer.memoryUsage",
Add reload workspace command
2020-07-01 12:57:59 +00:00
"onCommand:rust-analyzer.reloadWorkspace",
Limit depth to 1 when searching for Cargo.toml
2021-10-03 14:42:45 +00:00
"workspaceContains:*/Cargo.toml",
"workspaceContains:*/rust-project.json"
indexing infra
2018-08-13 10:46:05 +00:00
],
vscode extension: use esbuild instead of rollup.
2021-08-10 06:56:34 +00:00
"main": "./out/main",
you better run
2018-08-27 19:52:43 +00:00
"contributes": {
"taskDefinitions": [
{
"type": "cargo",
"required": [
"command"
],
"properties": {
"label": {
"type": "string"
},
"command": {
"type": "string"
},
"args": {
vscode: more type safety
2020-03-23 23:11:36 +00:00
"type": "array",
"items": {
"type": "string"
}
you better run
2018-08-27 19:52:43 +00:00
},
"env": {
vscode: more type safety
2020-03-23 23:11:36 +00:00
"type": "object",
"patternProperties": {
".+": {
"type": "string"
}
}
you better run
2018-08-27 19:52:43 +00:00
}
}
}
],
"commands": [
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.syntaxTree",
Add vscode support for range in SyntaxTreeParams This enables the client to use a command to either show the live-updating version of the syntax tree for the current file. Or optionally when a selected range is provided, we then provide a snapshot of the syntax tree for the range.
2019-03-03 19:21:40 +00:00
"title": "Show Syntax Tree",
Add category to the commands
2019-01-29 17:16:14 +00:00
"category": "Rust Analyzer"
you better run
2018-08-27 19:52:43 +00:00
},
Initial implementation of view-hir command
2020-12-28 18:29:58 +00:00
{
"command": "rust-analyzer.viewHir",
"title": "View Hir",
"category": "Rust Analyzer"
},
Add a "Debug ItemTree" LSP request
2021-05-21 21:59:52 +00:00
{
"command": "rust-analyzer.viewItemTree",
"title": "Debug ItemTree",
"category": "Rust Analyzer"
},
Allow viewing the crate graph in a webview
2021-05-11 14:15:31 +00:00
{
"command": "rust-analyzer.viewCrateGraph",
"title": "View Crate Graph",
"category": "Rust Analyzer"
},
Add "View Crate Graph (Full)"
2021-07-01 22:08:05 +00:00
{
"command": "rust-analyzer.viewFullCrateGraph",
"title": "View Crate Graph (Full)",
"category": "Rust Analyzer"
},
Use DocumentProvider instead of Hover
2019-11-19 17:06:10 +00:00
{
"command": "rust-analyzer.expandMacro",
"title": "Expand macro recursively",
"category": "Rust Analyzer"
},
you better run
2018-08-27 19:52:43 +00:00
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.matchingBrace",
Add category to the commands
2019-01-29 17:16:14 +00:00
"title": "Find matching brace",
"category": "Rust Analyzer"
you better run
2018-08-27 19:52:43 +00:00
},
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.parentModule",
Add category to the commands
2019-01-29 17:16:14 +00:00
"title": "Locate parent module",
"category": "Rust Analyzer"
you better run
2018-08-27 19:52:43 +00:00
},
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.joinLines",
Add category to the commands
2019-01-29 17:16:14 +00:00
"title": "Join lines",
"category": "Rust Analyzer"
you better run
2018-08-27 19:52:43 +00:00
},
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.run",
Add category to the commands
2019-01-29 17:16:14 +00:00
"title": "Run",
"category": "Rust Analyzer"
ad status command
2019-01-22 21:15:03 +00:00
},
Add **Copy Run Command Line** command for vscode This is useful when you want to, e.g., run a specific test in a terminal with `--release`.
2021-02-10 11:28:13 +00:00
{
"command": "rust-analyzer.copyRunCommandLine",
"title": "Copy Run Command Line",
"category": "Rust Analyzer"
},
"rust-analyzer.debug" command
2020-05-11 13:06:57 +00:00
{
"command": "rust-analyzer.debug",
"title": "Debug",
"category": "Rust Analyzer"
},
"rust-analyzer.newDebugConfig" command
2020-05-11 15:00:15 +00:00
{
"command": "rust-analyzer.newDebugConfig",
"title": "Generate launch configuration",
"category": "Rust Analyzer"
},
ad status command
2019-01-22 21:15:03 +00:00
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.analyzerStatus",
Add category to the commands
2019-01-29 17:16:14 +00:00
"title": "Status",
"category": "Rust Analyzer"
add gc request
2019-01-25 16:11:58 +00:00
},
Add a command to compute memory usage statistics
2020-07-07 10:10:14 +00:00
{
"command": "rust-analyzer.memoryUsage",
"title": "Memory Usage (Clears Database)",
"category": "Rust Analyzer"
},
add gc request
2019-01-25 16:11:58 +00:00
{
Add reload workspace command
2020-07-01 12:57:59 +00:00
"command": "rust-analyzer.reloadWorkspace",
"title": "Reload workspace",
Add category to the commands
2019-01-29 17:16:14 +00:00
"category": "Rust Analyzer"
Adds "restart server" command
2019-04-15 19:41:27 +00:00
},
{
"command": "rust-analyzer.reload",
"title": "Restart server",
"category": "Rust Analyzer"
Add regular onEnter command, allowing onEnter to be called without overriding the type command.
2020-02-02 01:21:04 +00:00
},
Add a command for updating the Github API token
2020-09-23 07:50:34 +00:00
{
"command": "rust-analyzer.updateGithubToken",
"title": "Update Github API token",
"category": "Rust Analyzer"
},
Add regular onEnter command, allowing onEnter to be called without overriding the type command.
2020-02-02 01:21:04 +00:00
{
"command": "rust-analyzer.onEnter",
"title": "Enhanced enter key",
"category": "Rust Analyzer"
Init implementation of structural search replace
2020-02-10 22:45:38 +00:00
},
{
"command": "rust-analyzer.ssr",
"title": "Structural Search Replace",
"category": "Rust Analyzer"
Improve server version info
2020-02-21 02:04:03 +00:00
},
{
"command": "rust-analyzer.serverVersion",
"title": "Show RA Version",
"category": "Rust Analyzer"
Introduce `toggle inlay hints` vscode command Users now can assign a shortcut for this command via the general vscode keybindings ui or `keybinding.json file` Closes: #4599
2020-05-25 00:47:33 +00:00
},
{
"command": "rust-analyzer.toggleInlayHints",
"title": "Toggle inlay hints",
"category": "Rust Analyzer"
WIP: Command to open docs under cursor
2020-08-30 08:02:29 +00:00
},
{
"command": "rust-analyzer.openDocs",
"title": "Open docs under cursor",
"category": "Rust Analyzer"
add open Cargo.toml action
2020-11-13 01:48:07 +00:00
},
{
"command": "rust-analyzer.openCargoToml",
"title": "Open Cargo.toml",
"category": "Rust Analyzer"
Add LSP request and VSCode command
2021-02-27 17:04:43 +00:00
},
{
"command": "rust-analyzer.peekTests",
"title": "Peek related tests",
"category": "Rust Analyzer"
Item up and down movers
2021-03-16 12:37:00 +00:00
},
{
"command": "rust-analyzer.moveItemUp",
"title": "Move item up",
"category": "Rust Analyzer"
},
{
"command": "rust-analyzer.moveItemDown",
"title": "Move item down",
"category": "Rust Analyzer"
you better run
2018-08-27 19:52:43 +00:00
}
],
"keybindings": [
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.parentModule",
Fix parentModule shortcut conflict The default parentModule shortcut conflicts with VSCode's built-in undo selection
2020-04-13 10:13:55 +00:00
"key": "ctrl+shift+u",
you better run
2018-08-27 19:52:43 +00:00
"when": "editorTextFocus && editorLangId == rust"
},
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.matchingBrace",
you better run
2018-08-27 19:52:43 +00:00
"key": "ctrl+shift+m",
"when": "editorTextFocus && editorLangId == rust"
},
{
align command naming
2019-01-28 11:43:07 +00:00
"command": "rust-analyzer.joinLines",
you better run
2018-08-27 19:52:43 +00:00
"key": "ctrl+shift+j",
"when": "editorTextFocus && editorLangId == rust"
}
indexing infra
2018-08-13 10:46:05 +00:00
],
Add a setting to disable custom syntax highlighting
2018-09-29 19:27:41 +00:00
"configuration": {
"type": "object",
Dynamically apply highlightingOn config Fixes #84
2018-10-06 20:53:12 +00:00
"title": "Rust Analyzer",
Add a setting to disable custom syntax highlighting
2018-09-29 19:27:41 +00:00
"properties": {
Add custom cargo runners
2020-06-18 19:20:13 +00:00
"rust-analyzer.cargoRunner": {
"type": [
"null",
"string"
],
"default": null,
"description": "Custom cargo runner extension ID."
},
Add runnable env support.
2020-07-02 16:47:40 +00:00
"rust-analyzer.runnableEnv": {
"anyOf": [
{
"type": "null"
},
{
"type": "array",
"items": {
"type": "object",
"properties": {
"mask": {
"type": "string",
"description": "Runnable name mask"
},
"env": {
"type": "object",
"description": "Variables in form of { \"key\": \"value\"}"
}
}
}
},
{
"type": "object",
"description": "Variables in form of { \"key\": \"value\"}"
}
],
"default": null,
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"markdownDescription": "Environment variables passed to the runnable launched using `Test` or `Debug` lens or `rust-analyzer.run` command."
Add runnable env support.
2020-07-02 16:47:40 +00:00
},
Add master config for inlayHints to make disabling easy
2020-05-08 07:28:15 +00:00
"rust-analyzer.inlayHints.enable": {
"type": "boolean",
"default": true,
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"description": "Whether to show inlay hints."
Add master config for inlayHints to make disabling easy
2020-05-08 07:28:15 +00:00
},
internal: ensure that client and server-side configs are not mixed up https://github.com/rust-lang/rust/issues/84647 would help big time here.
2021-04-28 10:06:46 +00:00
"rust-analyzer.inlayHints.smallerHints": {
"type": "boolean",
"default": true,
"description": "Whether inlay hints font size should be smaller than editor's font size."
},
New config in package.json
2020-04-02 09:55:04 +00:00
"rust-analyzer.updates.channel": {
"type": "string",
"enum": [
"stable",
"nightly"
],
"default": "stable",
"markdownEnumDescriptions": [
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"`stable` updates are shipped weekly, they don't contain cutting-edge features from VSCode proposed APIs but have less bugs in general.",
"`nightly` updates are shipped daily (extension updates automatically by downloading artifacts directly from GitHub), they contain cutting-edge features and latest bug fixes. These releases help us get your feedback very quickly and speed up rust-analyzer development **drastically**."
New config in package.json
2020-04-02 09:55:04 +00:00
],
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"markdownDescription": "Choose `nightly` updates to get the latest features and bug fixes every day. While `stable` releases occur weekly and don't contain cutting-edge features from VSCode proposed APIs."
New config in package.json
2020-04-02 09:55:04 +00:00
},
"rust-analyzer.updates.askBeforeDownload": {
"type": "boolean",
Code: automatically update the LSP server Most LSP extensions seem to do the same thing, and this is causing some confusion for users who don't notice the update prompt before Code hides it.
2021-06-14 14:44:26 +00:00
"default": false,
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"description": "Whether to ask for permission before downloading any files from the Internet."
New config in package.json
2020-04-02 09:55:04 +00:00
},
Rename extension config
2021-01-04 15:39:15 +00:00
"rust-analyzer.server.path": {
New config in package.json
2020-04-02 09:55:04 +00:00
"type": [
"null",
"string"
],
Exclude `rust-analyzer.server.path` from VS Code's sync feature By changing the scope of this configuration to `machine-overridible`, this setting becomes fully local for the VS Code instance the user is running. Having this setting excluded from syncing should help avoid inconveniences for users who have VS Code installed on two different operating systems, where the paths to the language server binary would very likely mismatch.
2021-08-01 10:00:41 +00:00
"scope": "machine-overridable",
New config in package.json
2020-04-02 09:55:04 +00:00
"default": null,
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"markdownDescription": "Path to rust-analyzer executable (points to bundled binary by default). If this is set, then `#rust-analyzer.updates.channel#` setting is not used"
New config in package.json
2020-04-02 09:55:04 +00:00
},
Add an option for extra env vars in the Code extension
2020-12-30 09:17:25 +00:00
"rust-analyzer.server.extraEnv": {
"type": [
"null",
"object"
],
"default": null,
"markdownDescription": "Extra environment variables that will be passed to the rust-analyzer executable. Useful for passing e.g. `RA_LOG` for debugging."
},
New config in package.json
2020-04-02 09:55:04 +00:00
"rust-analyzer.trace.server": {
"type": "string",
"scope": "window",
"enum": [
"off",
"messages",
"verbose"
],
"enumDescriptions": [
"No traces",
"Error only",
"Full log"
],
"default": "off",
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"description": "Trace requests to the rust-analyzer (this is usually overly verbose and not recommended for regular users)."
New config in package.json
2020-04-02 09:55:04 +00:00
},
"rust-analyzer.trace.extension": {
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"description": "Enable logging of VS Code extensions itself.",
New config in package.json
2020-04-02 09:55:04 +00:00
"type": "boolean",
"default": false
Add config for proc_macro
2020-04-12 16:05:33 +00:00
},
Configuration settings and source maps support
2020-04-29 10:10:42 +00:00
"rust-analyzer.debug.engine": {
better configuration enum items
2020-04-29 11:13:57 +00:00
"type": "string",
Configuration settings and source maps support
2020-04-29 10:10:42 +00:00
"enum": [
better configuration enum items
2020-04-29 11:13:57 +00:00
"auto",
"vadimcn.vscode-lldb",
"ms-vscode.cpptools"
Configuration settings and source maps support
2020-04-29 10:10:42 +00:00
],
better configuration enum items
2020-04-29 11:13:57 +00:00
"default": "auto",
package.json: Minor configuration spelling fix
2020-05-06 15:22:24 +00:00
"description": "Preferred debug engine.",
better configuration enum items
2020-04-29 11:13:57 +00:00
"markdownEnumDescriptions": [
pass Cargo errors to the Debug output channel
2020-04-30 12:25:04 +00:00
"First try to use [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb), if it's not installed try to use [MS C++ tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools).",
better configuration enum items
2020-04-29 11:13:57 +00:00
"Use [CodeLLDB](https://marketplace.visualstudio.com/items?itemName=vadimcn.vscode-lldb)",
"Use [MS C++ tools](https://marketplace.visualstudio.com/items?itemName=ms-vscode.cpptools)"
]
Configuration settings and source maps support
2020-04-29 10:10:42 +00:00
},
internal: ensure that client and server-side configs are not mixed up https://github.com/rust-lang/rust/issues/84647 would help big time here.
2021-04-28 10:06:46 +00:00
"rust-analyzer.debug.sourceFileMap": {
:arrow_up: package-lock.json
2021-05-08 09:20:06 +00:00
"type": [
"object",
"string"
],
Add special `auto` value for `debug.sourceFileMap`
2021-04-22 13:09:46 +00:00
"const": "auto",
Configuration settings and source maps support
2020-04-29 10:10:42 +00:00
"description": "Optional source file mappings passed to the debug engine.",
"default": {
better configuration enum items
2020-04-29 11:13:57 +00:00
"/rustc/<id>": "${env:USERPROFILE}/.rustup/toolchains/<toolchain-id>/lib/rustlib/src/rust"
Configuration settings and source maps support
2020-04-29 10:10:42 +00:00
}
Add additional debug options
2020-05-07 14:07:58 +00:00
},
"rust-analyzer.debug.openDebugPane" Co-authored-by: bjorn3 <bjorn3@users.noreply.github.com>
2020-05-08 16:22:26 +00:00
"rust-analyzer.debug.openDebugPane": {
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"markdownDescription": "Whether to open up the `Debug Panel` on debugging start.",
Add additional debug options
2020-05-07 14:07:58 +00:00
"type": "boolean",
"default": false
},
"rust-analyzer.debug.engineSettings": {
"type": "object",
"default": {},
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"markdownDescription": "Optional settings passed to the debug engine. Example: `{ \"lldb\": { \"terminal\":\"external\"} }`"
CodeLens configuration options.
2020-05-17 16:51:44 +00:00
},
Use objects instead of bools for markers in package.json
2021-06-15 06:32:53 +00:00
"$generated-start": {},
MergeBehavior -> ImportGranularity
2021-05-18 17:49:15 +00:00
"rust-analyzer.assist.importGranularity": {
"markdownDescription": "How imports should be grouped into use statements.",
Give MergeBehaviour variants better names
2021-05-10 19:03:50 +00:00
"default": "crate",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": "string",
"enum": [
MergeBehavior -> ImportGranularity
2021-05-18 17:49:15 +00:00
"preserve",
Give MergeBehaviour variants better names
2021-05-10 19:03:50 +00:00
"crate",
MergeBehavior -> ImportGranularity
2021-05-18 17:49:15 +00:00
"module",
"item"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
],
"enumDescriptions": [
MergeBehavior -> ImportGranularity
2021-05-18 17:49:15 +00:00
"Do not change the granularity of any imports and preserve the original structure written by the developer.",
"Merge imports from the same crate into a single use statement. Conversely, imports from different crates are split into separate statements.",
"Merge imports from the same module into a single use statement. Conversely, imports from different modules are split into separate statements.",
"Flatten imports so that each has its own use statement."
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
]
Add "rust-analyzer.lens.enable"
2020-05-18 07:27:00 +00:00
},
Replace ImportGranularity::Guess with guessing boolean flag
2021-05-18 18:21:47 +00:00
"rust-analyzer.assist.importEnforceGranularity": {
"markdownDescription": "Whether to enforce the import granularity setting for all files. If set to false rust-analyzer will try to keep import styles consistent per file.",
"default": false,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.assist.importPrefix": {
"markdownDescription": "The path structure for newly inserted paths to use.",
"default": "plain",
"type": "string",
"enum": [
"plain",
Give ImportPrefix variants better config names
2021-06-13 20:00:39 +00:00
"self",
"crate"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
],
"enumDescriptions": [
"Insert import paths relative to the current module, using up to one `super` prefix if the parent module contains the requested item.",
Give ImportPrefix variants better config names
2021-06-13 20:00:39 +00:00
"Insert import paths relative to the current module, using up to one `super` prefix if the parent module contains the requested item. Prefixes `self` in front of the path if it starts with a module.",
"Force import paths to be absolute by always starting them with `crate` or the extern crate name they come from."
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
]
CodeLens configuration options.
2020-05-17 16:51:44 +00:00
},
Make group imports configurable
2021-03-06 11:02:26 +00:00
"rust-analyzer.assist.importGroup": {
Fix: correct markdown link form.
2021-10-29 10:25:32 +00:00
"markdownDescription": "Group inserted imports by the [following order](https://rust-analyzer.github.io/manual.html#auto-import). Groups are separated by newlines.",
Make group imports configurable
2021-03-06 11:02:26 +00:00
"default": true,
"type": "boolean"
},
Allow to disable import insertion on single path glob imports
2021-06-18 21:11:56 +00:00
"rust-analyzer.assist.allowMergingIntoGlobImports": {
"markdownDescription": "Whether to allow import insertion to merge new imports into single path glob imports like `use std::fmt::*;`.",
"default": true,
"type": "boolean"
},
Add toggle to disable cache priming
2021-11-19 15:56:46 +00:00
"rust-analyzer.cache.warmup": {
"markdownDescription": "Warm up caches on project load.",
"default": true,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.callInfo.full": {
"markdownDescription": "Show function name and docs in parameter hints.",
"default": true,
"type": "boolean"
CodeLens configuration options.
2020-05-17 16:51:44 +00:00
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.cargo.autoreload": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Automatically refresh project info via `cargo metadata` on\n`Cargo.toml` changes.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
Add hover actions as LSP extension
2020-06-03 11:15:54 +00:00
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.cargo.allFeatures": {
Remove the need to manually sync config in package.json
2021-01-26 13:03:24 +00:00
"markdownDescription": "Activate all available features (`--all-features`).",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": false,
"type": "boolean"
Add method references CodeLens
2020-09-01 13:33:02 +00:00
},
Implement a config override for the default #[cfg(test)] in cargo crates Fixes crates which vanish when the 'test' cfg atom is set. Fix #7243. Fix #9203. Fix #7225.
2021-06-14 04:41:46 +00:00
"rust-analyzer.cargo.unsetTest": {
"markdownDescription": "Unsets `#[cfg(test)]` for the specified crates.",
"default": [
"core"
],
"type": "array",
"items": {
"type": "string"
}
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.cargo.features": {
"markdownDescription": "List of features to activate.",
"default": [],
"type": "array",
"items": {
"type": "string"
}
Add hover actions as LSP extension
2020-06-03 11:15:54 +00:00
},
Migrate to user-centric config name for `cargo check` stuff
2021-03-04 11:52:36 +00:00
"rust-analyzer.cargo.runBuildScripts": {
"markdownDescription": "Run build scripts (`build.rs`) for more precise code analysis.",
Make code completion "just work" in more cases
2021-03-08 11:52:16 +00:00
"default": true,
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": "boolean"
Document rust-project.json
2020-06-03 12:48:38 +00:00
},
feat: avoid checking the whole project during initial loading
2021-04-12 08:04:36 +00:00
"rust-analyzer.cargo.useRustcWrapperForBuildScripts": {
"markdownDescription": "Use `RUSTC_WRAPPER=rust-analyzer` when running build scripts to\navoid compiling unnecessary things.",
"default": true,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.cargo.noDefaultFeatures": {
"markdownDescription": "Do not activate the `default` feature.",
"default": false,
"type": "boolean"
Add Run|Debug hover actions
2020-06-06 11:30:29 +00:00
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.cargo.target": {
"markdownDescription": "Compilation target (target triple).",
"default": null,
"type": [
"null",
"string"
]
Add `rust-analyzer.gotoLocation` command
2020-06-10 20:01:19 +00:00
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.cargo.noSysroot": {
"markdownDescription": "Internal config for debugging, disables loading of sysroot crates.",
"default": false,
"type": "boolean"
Add Run|Debug hover actions
2020-06-06 11:30:29 +00:00
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.checkOnSave.enable": {
"markdownDescription": "Run specified `cargo check` command for diagnostics on save.",
"default": true,
"type": "boolean"
},
"rust-analyzer.checkOnSave.allFeatures": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Check with all features (`--all-features`).\nDefaults to `#rust-analyzer.cargo.allFeatures#`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": null,
"type": [
"null",
"boolean"
]
},
"rust-analyzer.checkOnSave.allTargets": {
Remove the need to manually sync config in package.json
2021-01-26 13:03:24 +00:00
"markdownDescription": "Check all targets and tests (`--all-targets`).",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.checkOnSave.command": {
"markdownDescription": "Cargo command to use for `cargo check`.",
"default": "check",
"type": "string"
},
"rust-analyzer.checkOnSave.noDefaultFeatures": {
"markdownDescription": "Do not activate the `default` feature.",
"default": null,
"type": [
"null",
"boolean"
]
},
"rust-analyzer.checkOnSave.target": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Check for a specific target. Defaults to\n`#rust-analyzer.cargo.target#`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": null,
"type": [
"null",
"string"
]
},
"rust-analyzer.checkOnSave.extraArgs": {
"markdownDescription": "Extra arguments for `cargo check`.",
"default": [],
Document rust-project.json
2020-06-03 12:48:38 +00:00
"type": "array",
"items": {
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": "string"
}
},
"rust-analyzer.checkOnSave.features": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "List of features to activate. Defaults to\n`#rust-analyzer.cargo.features#`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": null,
"type": [
"null",
"array"
],
"items": {
"type": "string"
}
},
"rust-analyzer.checkOnSave.overrideCommand": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Advanced option, fully override the command rust-analyzer uses for\nchecking. The command should include `--message-format=json` or\nsimilar option.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": null,
"type": [
"null",
"array"
],
"items": {
"type": "string"
}
},
"rust-analyzer.completion.addCallArgumentSnippets": {
Document that `addCallArgumentSnippets` requires `addCallParenthesis
2021-06-02 20:10:09 +00:00
"markdownDescription": "Whether to add argument snippets when completing functions.\nOnly applies when `#rust-analyzer.completion.addCallParenthesis#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.completion.addCallParenthesis": {
"markdownDescription": "Whether to add parenthesis when completing functions.",
"default": true,
"type": "boolean"
},
Regen docs
2021-10-04 20:13:12 +00:00
"rust-analyzer.completion.snippets": {
"markdownDescription": "Custom completion snippets.",
"default": {},
"type": "object"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.completion.postfix.enable": {
"markdownDescription": "Whether to show postfix snippets like `dbg`, `if`, `not`, etc.",
"default": true,
"type": "boolean"
},
"rust-analyzer.completion.autoimport.enable": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"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.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
Document rust-project.json
2020-06-03 12:48:38 +00:00
},
Add config setting for self-on-the-fly
2021-05-30 14:41:33 +00:00
"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,
"type": "boolean"
},
Add toggle for experimental diagnostics
2020-07-24 15:39:16 +00:00
"rust-analyzer.diagnostics.enable": {
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"markdownDescription": "Whether to show native rust-analyzer diagnostics.",
Add toggle for experimental diagnostics
2020-07-24 15:39:16 +00:00
"default": true,
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": "boolean"
Add toggle for experimental diagnostics
2020-07-24 15:39:16 +00:00
},
"rust-analyzer.diagnostics.enableExperimental": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show experimental rust-analyzer diagnostics that might\nhave more false positives than usual.",
Add toggle for experimental diagnostics
2020-07-24 15:39:16 +00:00
"default": true,
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": "boolean"
Add toggle for experimental diagnostics
2020-07-24 15:39:16 +00:00
},
Align diagnostics config with the rest of rust-analyzer
2020-08-18 14:03:15 +00:00
"rust-analyzer.diagnostics.disabled": {
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"markdownDescription": "List of rust-analyzer diagnostics to disable.",
"default": [],
Warnings as hint or info
2020-06-16 20:26:33 +00:00
"type": "array",
"items": {
"type": "string"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"uniqueItems": true
Warnings as hint or info
2020-06-16 20:26:33 +00:00
},
Code review feedback.
2021-04-21 22:09:37 +00:00
"rust-analyzer.diagnostics.remapPrefix": {
"markdownDescription": "Map of prefixes to be substituted when parsing diagnostic file paths.\nThis should be the reverse mapping of what is passed to `rustc` as `--remap-path-prefix`.",
Diagnostic Remap Path Prefixes added.
2021-04-21 03:03:35 +00:00
"default": {},
"type": "object"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.diagnostics.warningsAsHint": {
Fix incorrect setting descriptions Descriptions for diagnostic warning hint and info display were swapped. Fixes #8485. Signed-off-by: Lucas Schwiderski <lucas@lschwiderski.de>
2021-05-29 16:08:14 +00:00
"markdownDescription": "List of warnings that should be displayed with hint severity.\n\nThe warnings will be indicated by faded text or three dots in code\nand will not show up in the `Problems Panel`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": [],
Warnings as hint or info
2020-06-16 20:26:33 +00:00
"type": "array",
"items": {
"type": "string"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
}
Add a configuration option for the vscode extension
2020-08-12 13:06:55 +00:00
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.diagnostics.warningsAsInfo": {
Fix incorrect setting descriptions Descriptions for diagnostic warning hint and info display were swapped. Fixes #8485. Signed-off-by: Lucas Schwiderski <lucas@lschwiderski.de>
2021-05-29 16:08:14 +00:00
"markdownDescription": "List of warnings that should be displayed with info severity.\n\nThe warnings will be indicated by a blue squiggly underline in code\nand a blue icon in the `Problems Panel`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": [],
Add a configuration option for the vscode extension
2020-08-12 13:06:55 +00:00
"type": "array",
"items": {
"type": "string"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
}
Make MergeBehaviour configurable
2020-09-12 09:55:01 +00:00
},
Make it opt-in
2021-06-03 14:11:20 +00:00
"rust-analyzer.experimental.procAttrMacros": {
"markdownDescription": "Expand attribute macros.",
Enable attribute proc macros by default
2021-09-27 15:11:31 +00:00
"default": true,
Make it opt-in
2021-06-03 14:11:20 +00:00
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.files.watcher": {
"markdownDescription": "Controls file watching implementation.",
"default": "client",
"type": "string"
Support 'runnables' options in the vs code extension
2020-09-05 13:21:14 +00:00
},
Add config option to ignore directories
2021-01-26 13:18:01 +00:00
"rust-analyzer.files.excludeDirs": {
mention files.watcherExclude Co-authored-by: Laurențiu Nicola <lnicola@users.noreply.github.com>
2021-07-22 11:03:06 +00:00
"markdownDescription": "These directories will be ignored by rust-analyzer. They are\nrelative to the workspace root, and globs are not supported. You may\nalso need to add the folders to Code's `files.watcherExclude`.",
Add config option to ignore directories
2021-01-26 13:18:01 +00:00
"default": [],
"type": "array",
"items": {
"type": "string"
}
},
Updated docs.
2021-07-23 01:04:27 +00:00
"rust-analyzer.highlightRelated.references": {
"markdownDescription": "Enables highlighting of related references while hovering your mouse above any identifier.",
"default": true,
"type": "boolean"
},
"rust-analyzer.highlightRelated.exitPoints": {
"markdownDescription": "Enables highlighting of all exit points while hovering your mouse above any `return`, `?`, or return type arrow (`->`).",
"default": true,
"type": "boolean"
},
"rust-analyzer.highlightRelated.breakPoints": {
"markdownDescription": "Enables highlighting of related references while hovering your mouse `break`, `loop`, `while`, or `for` keywords.",
"default": true,
"type": "boolean"
},
"rust-analyzer.highlightRelated.yieldPoints": {
"markdownDescription": "Enables highlighting of all break points for a loop or block context while hovering your mouse above any `async` or `await` keywords.",
"default": true,
"type": "boolean"
},
minor: adjust config name
2021-05-17 15:37:06 +00:00
"rust-analyzer.highlighting.strings": {
"markdownDescription": "Use semantic tokens for strings.\n\nIn some editors (e.g. vscode) semantic tokens override other highlighting grammars.\nBy disabling semantic tokens for strings, other grammars can be used to highlight\ntheir contents.",
"default": true,
"type": "boolean"
},
Make documentation on hover configurable
2021-06-14 13:25:10 +00:00
"rust-analyzer.hover.documentation": {
"markdownDescription": "Whether to show documentation on hover.",
"default": true,
"type": "boolean"
},
"rust-analyzer.hover.linksInHover": {
"markdownDescription": "Use markdown syntax for links in hover.",
"default": true,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.hoverActions.debug": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Debug` action. Only applies when\n`#rust-analyzer.hoverActions.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.hoverActions.enable": {
"markdownDescription": "Whether to show HoverActions in Rust files.",
"default": true,
"type": "boolean"
},
"rust-analyzer.hoverActions.gotoTypeDef": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Go to Type Definition` action. Only applies when\n`#rust-analyzer.hoverActions.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.hoverActions.implementations": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Implementations` action. Only applies when\n`#rust-analyzer.hoverActions.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
Add function references hover action
2021-06-04 13:49:43 +00:00
"rust-analyzer.hoverActions.references": {
"markdownDescription": "Whether to show `References` action. Only applies when\n`#rust-analyzer.hoverActions.enable#` is set.",
"default": false,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.hoverActions.run": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Run` action. Only applies when\n`#rust-analyzer.hoverActions.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.inlayHints.chainingHints": {
"markdownDescription": "Whether to show inlay type hints for method chains.",
"default": true,
"type": "boolean"
},
"rust-analyzer.inlayHints.maxLength": {
Limit the hints size by default
2021-03-23 17:04:48 +00:00
"markdownDescription": "Maximum length for inlay hints. Set to null to have an unlimited length.",
Bump the default hint length
2021-03-23 17:43:55 +00:00
"default": 25,
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": [
"null",
"integer"
Make ImportPrefix a configuration option
2020-10-05 15:41:49 +00:00
],
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"minimum": 0
},
"rust-analyzer.inlayHints.parameterHints": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show function parameter name inlay hints at the call\nsite.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.inlayHints.typeHints": {
"markdownDescription": "Whether to show inlay type hints for variables.",
"default": true,
"type": "boolean"
},
inlay hints: add the option to always show constructor inlay hints
2021-11-13 23:12:29 +00:00
"rust-analyzer.inlayHints.hideNamedConstructorHints": {
"markdownDescription": "Whether to hide inlay hints for constructors.",
flip the default
2021-11-13 23:39:34 +00:00
"default": false,
inlay hints: add the option to always show constructor inlay hints
2021-11-13 23:12:29 +00:00
"type": "boolean"
},
feat: make join lines behavior configurable closes #9492
2021-07-05 20:31:44 +00:00
"rust-analyzer.joinLines.joinElseIf": {
"markdownDescription": "Join lines inserts else between consecutive ifs.",
"default": true,
"type": "boolean"
},
"rust-analyzer.joinLines.removeTrailingComma": {
"markdownDescription": "Join lines removes trailing commas.",
"default": true,
"type": "boolean"
},
"rust-analyzer.joinLines.unwrapTrivialBlock": {
"markdownDescription": "Join lines unwraps trivial blocks.",
"default": true,
"type": "boolean"
},
feat: join lines merges assignments
2021-08-22 18:28:39 +00:00
"rust-analyzer.joinLines.joinAssignments": {
"markdownDescription": "Join lines merges consecutive declaration and initialization of an assignment.",
"default": true,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.lens.debug": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Debug` lens. Only applies when\n`#rust-analyzer.lens.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.lens.enable": {
"markdownDescription": "Whether to show CodeLens in Rust files.",
"default": true,
"type": "boolean"
},
"rust-analyzer.lens.implementations": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Implementations` lens. Only applies when\n`#rust-analyzer.lens.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.lens.run": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Run` lens. Only applies when\n`#rust-analyzer.lens.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": true,
"type": "boolean"
},
"rust-analyzer.lens.methodReferences": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Whether to show `Method References` lens. Only applies when\n`#rust-analyzer.lens.enable#` is set.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": false,
"type": "boolean"
},
Add References code lens. For Struct, Enum, Union and Trait symbols.
2021-01-23 13:56:20 +00:00
"rust-analyzer.lens.references": {
need to update some generated files.
2021-10-04 07:30:46 +00:00
"markdownDescription": "Whether to show `References` lens for Struct, Enum, Union and Trait.\nOnly applies when `#rust-analyzer.lens.enable#` is set.",
Add enum variant references CodeLens.
2021-10-04 07:18:31 +00:00
"default": false,
"type": "boolean"
},
"rust-analyzer.lens.enumVariantReferences": {
need to update some generated files.
2021-10-04 07:30:46 +00:00
"markdownDescription": "Whether to show `References` lens for Enum Variants.\nOnly applies when `#rust-analyzer.lens.enable#` is set.",
Add References code lens. For Struct, Enum, Union and Trait symbols.
2021-01-23 13:56:20 +00:00
"default": false,
"type": "boolean"
},
feat: gate custom clint-side commands behind capabilities Some features of rust-analyzer requires support for custom commands on the client side. Specifically, hover & code lens need this. Stock LSP doesn't have a way for the server to know which client-side commands are available. For that reason, we historically were just sending the commands, not worrying whether the client supports then or not. That's not really great though, so in this PR we add infrastructure for the client to explicitly opt-into custom commands, via `extensions` field of the ClientCapabilities. To preserve backwards compatability, if the client doesn't set the field, we assume that it does support all custom commands. In the future, we'll start treating that case as if the client doesn't support commands. So, if you maintain a rust-analyzer client and implement `rust-analyzer/runSingle` and such, please also advertise this via a capability.
2021-07-30 16:16:33 +00:00
"rust-analyzer.lens.forceCustomCommands": {
"markdownDescription": "Internal config: use custom client-side commands even when the\nclient doesn't set the corresponding capability.",
"default": true,
"type": "boolean"
},
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"rust-analyzer.linkedProjects": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Disable project auto-discovery in favor of explicitly specified set\nof projects.\n\nElements must be paths pointing to `Cargo.toml`,\n`rust-project.json`, or JSON objects in `rust-project.json` format.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": [],
"type": "array",
"items": {
"type": [
"string",
"object"
]
}
},
"rust-analyzer.lruCapacity": {
Remove the need to manually sync config in package.json
2021-01-26 13:03:24 +00:00
"markdownDescription": "Number of syntax trees rust-analyzer keeps in memory. Defaults to 128.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": null,
"type": [
"null",
"integer"
Make ImportPrefix a configuration option
2020-10-05 15:41:49 +00:00
],
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"minimum": 0
},
"rust-analyzer.notifications.cargoTomlNotFound": {
"markdownDescription": "Whether to show `can't find Cargo.toml` error message.",
"default": true,
"type": "boolean"
},
"rust-analyzer.procMacro.enable": {
Migrate to user-centric config name for `cargo check` stuff
2021-03-04 11:52:36 +00:00
"markdownDescription": "Enable support for procedural macros, implies `#rust-analyzer.cargo.runBuildScripts#`.",
Enable proc-macros by default
2021-03-15 15:19:08 +00:00
"default": true,
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": "boolean"
Make ImportPrefix a configuration option
2020-10-05 15:41:49 +00:00
},
More maintainable config Rather than eagerly converting JSON, we losslessly keep it as is, and change the shape of user-submitted data at the last moment. This also allows us to remove a bunch of wrong Defaults
2021-01-06 10:54:28 +00:00
"rust-analyzer.procMacro.server": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Internal config, path to proc-macro server executable (typically,\nthis is rust-analyzer itself, but we override this in tests).",
More maintainable config Rather than eagerly converting JSON, we losslessly keep it as is, and change the shape of user-submitted data at the last moment. This also allows us to remove a bunch of wrong Defaults
2021-01-06 10:54:28 +00:00
"default": null,
"type": [
"null",
"string"
]
},
Support 'runnables' options in the vs code extension
2020-09-05 13:21:14 +00:00
"rust-analyzer.runnables.overrideCargo": {
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"markdownDescription": "Command to be executed instead of 'cargo' for runnables.",
"default": null,
Support 'runnables' options in the vs code extension
2020-09-05 13:21:14 +00:00
"type": [
"null",
"string"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
]
Support 'runnables' options in the vs code extension
2020-09-05 13:21:14 +00:00
},
"rust-analyzer.runnables.cargoExtraArgs": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Additional arguments to be passed to cargo for runnables such as\ntests or binaries. For example, it may be `--release`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": [],
Support 'runnables' options in the vs code extension
2020-09-05 13:21:14 +00:00
"type": "array",
"items": {
"type": "string"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
}
Add support for loading rustc private crates
2020-11-10 20:50:05 +00:00
},
Address review comments
2020-11-12 17:46:47 +00:00
"rust-analyzer.rustcSource": {
Document rustc source auto-discovery
2021-10-14 05:49:22 +00:00
"markdownDescription": "Path to the Cargo.toml of the rust compiler workspace, for usage in rustc_private\nprojects, or \"discover\" to try to automatically find it if the `rustc-dev` component\nis installed.\n\nAny project which uses rust-analyzer with the rustcPrivate\ncrates must set `[package.metadata.rust-analyzer] rustc_private=true` to use it.\n\nThis option does not take effect until rust-analyzer is restarted.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": null,
Address review comments
2020-11-12 17:46:47 +00:00
"type": [
"null",
"string"
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
]
},
"rust-analyzer.rustfmt.extraArgs": {
Clean up descriptions for settings Use two consecutive newlines (`\n\n`) to actually continue text on a new line. Use proper markup to reference related settings. Consistently format references to files, editor commands, command line arguments, files, etc. as `code`. Fix typos, add missing full-stops, add missing default values.
2020-12-22 00:15:50 +00:00
"markdownDescription": "Additional arguments to `rustfmt`.",
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"default": [],
"type": "array",
"items": {
"type": "string"
}
},
"rust-analyzer.rustfmt.overrideCommand": {
Make code less surprising Theres no reason to have literal `\n\n` in the source code
2021-03-09 11:43:05 +00:00
"markdownDescription": "Advanced option, fully override the command rust-analyzer uses for\nformatting.",
Add support for loading rustc private crates
2020-11-10 20:50:05 +00:00
"default": null,
Make config.rs a single source of truth for configuration. Configuration is editor-independent. For this reason, we pick JSON-schema as the repr of the source of truth. We do specify it using rust-macros and some quick&dirty hackery though. The idea for syncing truth with package.json is to just do that manually, but there's a test to check that they are actually synced. There's CLI to print config's json schema: $ rust-analyzer --print-config-schema We go with a CLI rather than LSP request/response to make it easier to incorporate the thing into extension's static config. This is roughtly how we put the thing in package.json.
2020-12-02 14:31:24 +00:00
"type": [
"null",
"array"
],
"items": {
"type": "string"
}
Remove the need to manually sync config in package.json
2021-01-26 13:03:24 +00:00
},
implement range formatting
2021-05-04 21:13:51 +00:00
"rust-analyzer.rustfmt.enableRangeFormatting": {
"markdownDescription": "Enables the use of rustfmt's unstable range formatting command for the\n`textDocument/rangeFormatting` request. The rustfmt option is unstable and only\navailable on a nightly build.",
"default": false,
"type": "boolean"
},
Add new LSP extension for workspace symbol lookup The new extension allows filtering of workspace symbool lookup results by search scope or search kind. Filtering can be configured in 3 different ways: - The '#' or '*' markers can be added inline with the symbol lookup query. The '#' marker means symbols should be looked up in the current workspace and any dependencies. If not specified, only current workspace is considered. The '*' marker means all kinds of symbols should be looked up (types, functions, etc). If not specified, only type symbols are returned. - Each LSP request can take an optional search_scope or search_kind argument query parameter. - Finally there are 2 global config options that can be set for all requests served by the active RA instance. Add support for setting the global config options to the VSCode extension. The extension does not use the per-request way, but it's useful for other IDEs. The latest version of VSCode filters out the inline markers, so currently the only reasonable way to use the new functionality is via the global config.
2021-02-23 12:03:31 +00:00
"rust-analyzer.workspace.symbol.search.scope": {
"markdownDescription": "Workspace symbol search scope.",
"default": "workspace",
"type": "string",
"enum": [
"workspace",
"workspace_and_dependencies"
],
"enumDescriptions": [
"Search in current workspace only",
"Search in current workspace and dependencies"
]
},
"rust-analyzer.workspace.symbol.search.kind": {
"markdownDescription": "Workspace symbol search kind.",
"default": "only_types",
"type": "string",
"enum": [
"only_types",
"all_symbols"
],
"enumDescriptions": [
"Search for types only",
"Search for all symbols kinds"
]
},
Use objects instead of bools for markers in package.json
2021-06-15 06:32:53 +00:00
"$generated-end": {}
Add a setting to disable custom syntax highlighting
2018-09-29 19:27:41 +00:00
}
},
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"problemPatterns": [
you better run
2018-08-27 19:52:43 +00:00
{
"name": "rustc",
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"patterns": [
you better run
2018-08-27 19:52:43 +00:00
{
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"regexp": "^(warning|warn|error)(?:\\[(.*?)\\])?: (.*)$",
you better run
2018-08-27 19:52:43 +00:00
"severity": 1,
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"code": 2,
"message": 3
you better run
2018-08-27 19:52:43 +00:00
},
{
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"regexp": "^[\\s->=]*(.*?):(\\d*):(\\d*)\\s*$",
"file": 1,
"line": 2,
"column": 3
you better run
2018-08-27 19:52:43 +00:00
}
]
Add a rudimentary json regex to get at information like `endLine`
2019-12-15 16:12:52 +00:00
},
{
"name": "rustc-json",
Properly format json
2019-12-15 16:19:41 +00:00
"patterns": [
{
"regexp": "^.*\"message\":{\"message\":\"([^\"]*).*?\"file_name\":\"([^\"]+).*?\"line_start\":(\\d+).*?\"line_end\":(\\d+).*?\"column_start\":(\\d+).*?\"column_end\":(\\d+).*}$",
"message": 1,
"file": 2,
"line": 3,
"endLine": 4,
"column": 5,
"endColumn": 6
}
]
you better run
2018-08-27 19:52:43 +00:00
}
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
],
vscode: add highlighting of syntax tree
2020-04-02 02:38:52 +00:00
"languages": [
{
"id": "ra_syntax_tree",
"extensions": [
".rast"
]
add a language configuration for VS Code
2020-12-12 00:31:00 +00:00
},
{
"id": "rust",
"extensions": [
".rs"
],
"aliases": [
"Rust",
"rs"
],
"configuration": "language-configuration.json"
vscode: add highlighting of syntax tree
2020-04-02 02:38:52 +00:00
}
],
"grammars": [
{
"language": "ra_syntax_tree",
"scopeName": "source.ra_syntax_tree",
"path": "ra_syntax_tree.tmGrammar.json"
}
],
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"problemMatchers": [
{
"name": "rustc",
ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's owner and source. VSCode LSP updated to specify owner.
2020-07-23 05:32:54 +00:00
"owner": "rustc",
"source": "rustc",
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"fileLocation": [
ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's owner and source. VSCode LSP updated to specify owner.
2020-07-23 05:32:54 +00:00
"autoDetect",
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
"${workspaceRoot}"
],
Use named multiline Problem Matcher Now that https://github.com/Microsoft/vscode/pull/65840 is in the latest release we can use the first commit from https://github.com/rust-analyzer/rust-analyzer/pull/408
2019-02-18 18:12:54 +00:00
"pattern": "$rustc"
recover rustc-watch problemMatchers
2019-04-14 10:45:36 +00:00
},
Add a rudimentary json regex to get at information like `endLine`
2019-12-15 16:12:52 +00:00
{
"name": "rustc-json",
ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's owner and source. VSCode LSP updated to specify owner.
2020-07-23 05:32:54 +00:00
"owner": "rustc",
"source": "rustc",
Add a rudimentary json regex to get at information like `endLine`
2019-12-15 16:12:52 +00:00
"fileLocation": [
ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's owner and source. VSCode LSP updated to specify owner.
2020-07-23 05:32:54 +00:00
"autoDetect",
Add a rudimentary json regex to get at information like `endLine`
2019-12-15 16:12:52 +00:00
"${workspaceRoot}"
],
"pattern": "$rustc-json"
},
recover rustc-watch problemMatchers
2019-04-14 10:45:36 +00:00
{
"name": "rustc-watch",
ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's owner and source. VSCode LSP updated to specify owner.
2020-07-23 05:32:54 +00:00
"owner": "rustc",
"source": "rustc",
recover rustc-watch problemMatchers
2019-04-14 10:45:36 +00:00
"fileLocation": [
ProblemMatcher auto detects relative/absolute paths and matches VSCode LSP's owner and source. VSCode LSP updated to specify owner.
2020-07-23 05:32:54 +00:00
"autoDetect",
recover rustc-watch problemMatchers
2019-04-14 10:45:36 +00:00
"${workspaceRoot}"
],
"background": {
"beginsPattern": "^\\[Running\\b",
"endsPattern": "^\\[Finished running\\b"
},
"pattern": "$rustc"
fix regex and add rustc-watch problem matcher
2018-12-30 17:24:07 +00:00
}
Use ThemeColor and add support for light themes
2019-05-21 11:04:54 +00:00
],
"colors": [
{
Make inlay hints colors more configurable
2020-08-25 23:37:58 +00:00
"id": "rust_analyzer.inlayHints.foreground",
"description": "Foreground color of inlay hints (is overriden by more specific rust_analyzer.inlayHints.foreground.* configurations)",
Show type decorators
2019-07-23 13:38:21 +00:00
"defaults": {
"dark": "#A0A0A0F0",
"light": "#747474",
"highContrast": "#BEBEBE"
}
vscode: add support for light themes and color customization for syntax tree highlights
2020-04-01 22:20:08 +00:00
},
Make inlay hints colors more configurable
2020-08-25 23:37:58 +00:00
{
"id": "rust_analyzer.inlayHints.background",
"description": "Background color of inlay hints (is overriden by more specific rust_analyzer.inlayHints.background.* configurations)",
"defaults": {
"dark": "#11223300",
"light": "#11223300",
"highContrast": "#11223300"
}
},
{
"id": "rust_analyzer.inlayHints.foreground.typeHints",
"description": "Foreground color of inlay type hints for variables (overrides rust_analyzer.inlayHints.foreground)",
"defaults": {
"dark": "rust_analyzer.inlayHints.foreground",
"light": "rust_analyzer.inlayHints.foreground",
"highContrast": "rust_analyzer.inlayHints.foreground"
}
},
{
"id": "rust_analyzer.inlayHints.foreground.chainingHints",
"description": "Foreground color of inlay type hints for method chains (overrides rust_analyzer.inlayHints.foreground)",
"defaults": {
"dark": "rust_analyzer.inlayHints.foreground",
"light": "rust_analyzer.inlayHints.foreground",
"highContrast": "rust_analyzer.inlayHints.foreground"
}
},
{
"id": "rust_analyzer.inlayHints.foreground.parameterHints",
"description": "Foreground color of function parameter name inlay hints at the call site (overrides rust_analyzer.inlayHints.foreground)",
"defaults": {
"dark": "rust_analyzer.inlayHints.foreground",
"light": "rust_analyzer.inlayHints.foreground",
"highContrast": "rust_analyzer.inlayHints.foreground"
}
},
{
"id": "rust_analyzer.inlayHints.background.typeHints",
"description": "Background color of inlay type hints for variables (overrides rust_analyzer.inlayHints.background)",
"defaults": {
"dark": "rust_analyzer.inlayHints.background",
"light": "rust_analyzer.inlayHints.background",
"highContrast": "rust_analyzer.inlayHints.background"
}
},
{
"id": "rust_analyzer.inlayHints.background.chainingHints",
"description": "Background color of inlay type hints for method chains (overrides rust_analyzer.inlayHints.background)",
"defaults": {
"dark": "rust_analyzer.inlayHints.background",
"light": "rust_analyzer.inlayHints.background",
"highContrast": "rust_analyzer.inlayHints.background"
}
},
{
"id": "rust_analyzer.inlayHints.background.parameterHints",
"description": "Background color of function parameter name inlay hints at the call site (overrides rust_analyzer.inlayHints.background)",
"defaults": {
"dark": "rust_analyzer.inlayHints.background",
"light": "rust_analyzer.inlayHints.background",
"highContrast": "rust_analyzer.inlayHints.background"
}
},
vscode: add support for light themes and color customization for syntax tree highlights
2020-04-01 22:20:08 +00:00
{
"id": "rust_analyzer.syntaxTreeBorder",
"description": "Color of the border displayed in the Rust source code for the selected syntax node (see \"Show Syntax Tree\" command)",
"defaults": {
"dark": "#ffffff",
"light": "#b700ff",
"highContrast": "#b700ff"
}
Use ThemeColor and add support for light themes
2019-05-21 11:04:54 +00:00
}
wip
2020-02-26 17:20:38 +00:00
],
Better highlightign API
2020-02-26 18:39:32 +00:00
"semanticTokenTypes": [
{
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
"id": "attribute",
"description": "Style for attributes"
Color constants
2020-02-26 22:16:57 +00:00
},
Add boolean literals to package.json
2020-05-25 08:39:56 +00:00
{
"id": "boolean",
"description": "Style for boolean literals",
"superType": "keyword"
},
Color constants
2020-02-26 22:16:57 +00:00
{
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
"id": "builtinType",
Set semantic tokens supertypes
2020-04-03 10:24:11 +00:00
"description": "Style for builtin types",
"superType": "type"
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
},
{
"id": "lifetime",
"description": "Style for lifetimes"
},
{
Add self keyword semantic token type
2020-05-25 08:51:56 +00:00
"id": "selfKeyword",
"description": "Style for the self keyword",
"superType": "keyword"
},
{
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
"id": "typeAlias",
Set semantic tokens supertypes
2020-04-03 10:24:11 +00:00
"description": "Style for type aliases",
"superType": "type"
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
},
{
"id": "union",
Set semantic tokens supertypes
2020-04-03 10:24:11 +00:00
"description": "Style for C-style untagged unions",
"superType": "type"
Add semantic tag for unresolved references This is a quick way to implement unresolved reference diagnostics. For example, adding to VS Code config "editor.tokenColorCustomizationsExperimental": { "unresolvedReference": "#FF0000" }, will highlight all unresolved refs in red.
2020-04-18 18:59:22 +00:00
},
{
"id": "unresolvedReference",
"description": "Style for names which can not be resolved due to compilation errors"
Specify cotributed semanticTokenTypes in package.json
2020-05-04 11:10:59 +00:00
},
{
"id": "formatSpecifier",
"description": "Style for {} placeholders in format strings"
Fix highlighting of injected attributes
2021-02-09 14:41:12 +00:00
},
{
"id": "punctuation",
"description": "generic punctuation"
},
{
"id": "parenthesis",
"description": "( or )",
"superType": "punctuation"
},
{
"id": "bracket",
"description": "[ or ]",
"superType": "punctuation"
},
{
"id": "brace",
"description": "{ or }",
"superType": "punctuation"
},
{
"id": "angle",
"description": "< or >",
"superType": "punctuation"
},
{
"id": "comma",
"description": ",",
"superType": "punctuation"
},
{
"id": "colon",
"description": ":",
"superType": "punctuation"
},
{
"id": "semicolon",
"description": ";",
"superType": "punctuation"
},
{
"id": "dot",
"description": ".",
"superType": "punctuation"
Better highlightign API
2020-02-26 18:39:32 +00:00
}
],
"semanticTokenModifiers": [
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
{
"id": "async",
"description": "Style for async functions and the `async` and `await` keywords"
},
Color attribute functions
2020-05-13 04:58:51 +00:00
{
"id": "attribute",
"description": "Style for elements within attributes"
},
Better highlightign API
2020-02-26 18:39:32 +00:00
{
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
"id": "constant",
"description": "Style for compile-time constants"
Better highlightign API
2020-02-26 18:39:32 +00:00
},
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
{
"id": "callable",
"description": "Style for locals whose types implements one of the `Fn*` traits"
},
{
"id": "consuming",
"description": "Style for locals that are being consumed when use in a function call"
},
Better highlightign API
2020-02-26 18:39:32 +00:00
{
Make control token modifier less ambiguous In textmate, keyword.control is used for all kinds of things; in fact, the default scope mapping for keyword is keyword.control! So let's add a less ambiguous controlFlow modifier See Microsoft/vscode#94367
2020-04-05 12:46:07 +00:00
"id": "controlFlow",
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
"description": "Style for control-flow related tokens, this includes the `?` operator"
Better highlightign API
2020-02-26 18:39:32 +00:00
},
{
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
"id": "definition",
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
"description": "Style for mutable bindings"
Better highlightign API
2020-02-26 18:39:32 +00:00
},
{
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
"id": "injected",
"description": "Style for doc-string injected highlighting like rust source blocks in documentation"
Document "consuming" semantic tokens modifier
2020-09-15 21:53:37 +00:00
},
{
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
"id": "intraDocLink",
"description": "Style for intra doc links in doc-strings"
Editor: Code: Add callable to package.json
2020-10-16 12:06:52 +00:00
},
{
Update `semanticTokenModifiers` in package.json
2021-09-25 12:10:46 +00:00
"id": "library",
"description": "Style for items that are defined outside of the current crate"
},
{
"id": "mutable",
"description": "Style for mutable locals and statics as well as functions taking `&mut self`"
},
{
"id": "public",
"description": "Style tems that are from the current crate and are `pub`"
},
{
"id": "reference",
"description": "Style for locals behind a reference and functions taking `self` by reference"
},
{
"id": "trait",
"description": "Style for associated trait items"
},
{
"id": "unsafe",
"description": "Style for unsafe operations, like unsafe function calls, as well as the `unsafe` token"
Better highlightign API
2020-02-26 18:39:32 +00:00
}
],
Fix semantic coloring
2020-04-02 13:52:25 +00:00
"semanticTokenScopes": [
Set attr scope
2020-02-27 17:31:54 +00:00
{
Fix semantic coloring
2020-04-02 13:52:25 +00:00
"language": "rust",
"scopes": {
"attribute": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"meta.attribute.rust"
Fix semantic coloring
2020-04-02 13:52:25 +00:00
],
Color attribute functions
2020-05-13 04:58:51 +00:00
"function.attribute": [
"entity.name.function.attribute.rust"
],
Highlight `true` and `false` as literals
2020-05-21 16:40:52 +00:00
"boolean": [
"constant.language.boolean.rust"
],
Fix semantic coloring
2020-04-02 13:52:25 +00:00
"builtinType": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"support.type.primitive.rust"
Fix semantic coloring
2020-04-02 13:52:25 +00:00
],
"lifetime": [
Change lifetimes back to keyword-ish, tweak builtins for consistency between TextMate and semantic
2020-05-10 20:32:42 +00:00
"storage.modifier.lifetime.rust"
Fix semantic coloring
2020-04-02 13:52:25 +00:00
],
"typeAlias": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"entity.name.type.typeAlias.rust"
Fix semantic coloring
2020-04-02 13:52:25 +00:00
],
"union": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"entity.name.type.union.rust"
Fix semantic coloring
2020-04-02 13:52:25 +00:00
],
Use the correct color for structs This works around https://github.com/microsoft/vscode/issues/97162
2020-05-07 16:46:58 +00:00
"struct": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"entity.name.type.struct.rust"
Use the correct color for structs This works around https://github.com/microsoft/vscode/issues/97162
2020-05-07 16:46:58 +00:00
],
Better mapping to TextMate scopes for keywords https://github.com/microsoft/vscode/issues/94367#issuecomment-608629883
2020-05-06 17:03:17 +00:00
"keyword": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"keyword.other.rust"
Better mapping to TextMate scopes for keywords https://github.com/microsoft/vscode/issues/94367#issuecomment-608629883
2020-05-06 17:03:17 +00:00
],
"keyword.controlFlow": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"keyword.control.rust"
Better mapping to TextMate scopes for keywords https://github.com/microsoft/vscode/issues/94367#issuecomment-608629883
2020-05-06 17:03:17 +00:00
],
Fix semantic coloring
2020-04-02 13:52:25 +00:00
"variable.constant": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"variable.other.constant.rust"
Tweak the textmate fallback scopes to be consistent with builtin TextMate grammar and other languages
2020-05-09 17:23:32 +00:00
],
"formatSpecifier": [
Use .rust suffix on scopes
2020-05-12 15:31:43 +00:00
"punctuation.section.embedded.rust"
Mark up statics and mutables
2020-05-09 20:19:29 +00:00
],
"*.mutable": [
"markup.underline"
Fix semantic coloring
2020-04-02 13:52:25 +00:00
]
Cleanup highlighting tags
2020-02-28 11:06:54 +00:00
}
wip
2020-02-26 17:20:38 +00:00
}
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
],
"menus": {
"commandPalette": [
{
"command": "rust-analyzer.syntaxTree",
"when": "inRustProject"
},
Initial implementation of view-hir command
2020-12-28 18:29:58 +00:00
{
"command": "rust-analyzer.viewHir",
"when": "inRustProject"
},
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
{
"command": "rust-analyzer.expandMacro",
"when": "inRustProject"
},
{
"command": "rust-analyzer.matchingBrace",
"when": "inRustProject"
},
{
"command": "rust-analyzer.parentModule",
"when": "inRustProject"
},
{
"command": "rust-analyzer.joinLines",
"when": "inRustProject"
},
{
"command": "rust-analyzer.run",
"when": "inRustProject"
},
{
"command": "rust-analyzer.debug",
"when": "inRustProject"
},
{
"command": "rust-analyzer.newDebugConfig",
"when": "inRustProject"
},
{
"command": "rust-analyzer.analyzerStatus",
"when": "inRustProject"
},
Add a command to compute memory usage statistics
2020-07-07 10:10:14 +00:00
{
"command": "rust-analyzer.memoryUsage",
"when": "inRustProject"
},
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
{
Add reload workspace command
2020-07-01 12:57:59 +00:00
"command": "rust-analyzer.reloadWorkspace",
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
"when": "inRustProject"
},
{
"command": "rust-analyzer.reload",
"when": "inRustProject"
},
Add a command for updating the Github API token
2020-09-23 07:50:34 +00:00
{
"command": "rust-analyzer.updateGithubToken",
"when": "inRustProject"
},
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
{
"command": "rust-analyzer.onEnter",
"when": "inRustProject"
},
{
"command": "rust-analyzer.ssr",
"when": "inRustProject"
},
{
"command": "rust-analyzer.serverVersion",
"when": "inRustProject"
},
{
"command": "rust-analyzer.toggleInlayHints",
"when": "inRustProject"
WIP: Command to open docs under cursor
2020-08-30 08:02:29 +00:00
},
{
"command": "rust-analyzer.openDocs",
"when": "inRustProject"
add open Cargo.toml action
2020-11-13 01:48:07 +00:00
},
{
"command": "rust-analyzer.openCargoToml",
"when": "inRustProject"
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
}
Add progress reporting
2021-02-27 18:07:23 +00:00
],
"editor/context": [
{
"command": "rust-analyzer.peekTests",
"when": "inRustProject",
"group": "navigation@1000"
}
Add `inRustProject` when-clause for commands.
2020-05-27 16:40:13 +00:00
]
}
you better run
2018-08-27 19:52:43 +00:00
}
Diagnostic Remap Path Prefixes added.
2021-04-21 03:03:35 +00:00
}
Reference in a new issue Copy permalink