aboutsummaryrefslogtreecommitdiff
path: root/editors/code
diff options
context:
space:
mode:
authorbors[bot] <26634292+bors[bot]@users.noreply.github.com>2021-05-17 15:41:56 +0100
committerGitHub <[email protected]>2021-05-17 15:41:56 +0100
commitf9d4a9eaee6f86d9bd60cf6d18ec744b56696135 (patch)
tree31c5c36a446ca3cd123309ac85dc39e0e23cdc74 /editors/code
parentfa02911078cfa1b3d3b9fb2cbbed9d1de98cd88e (diff)
parent7ae3967e5739b786fcd3f7b7b333c73f2c38e8dd (diff)
Merge #8795
8795: Allow semantic tokens for strings to be disabled r=matklad a=djrenren Fixes https://github.com/rust-analyzer/rust-analyzer/issues/7111 Pretty straightforward change, but open to any suggestions if there's a more recommended testing strategy than what I went with. Co-authored-by: John Renner <[email protected]>
Diffstat (limited to 'editors/code')
-rw-r--r--editors/code/package.json5
1 files changed, 5 insertions, 0 deletions
diff --git a/editors/code/package.json b/editors/code/package.json
index 0f38a1673..14cffac06 100644
--- a/editors/code/package.json
+++ b/editors/code/package.json
@@ -778,6 +778,11 @@
778 "type": "string" 778 "type": "string"
779 } 779 }
780 }, 780 },
781 "rust-analyzer.semanticStringTokens": {
782 "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.",
783 "default": true,
784 "type": "boolean"
785 },
781 "$generated-end": false 786 "$generated-end": false
782 } 787 }
783 }, 788 },