Closed
Description
Refs: microsoft/vscode-anycode#38, microsoft/vscode-anycode#39
- anyOS @daviddossett
- anyOS @joaomoreno
Complexity: 3
Anycode has seen improvements that should make it less aggressive in indexing and less likely to conflict with a "real" language extensions. Test the following
- make sure anycode is installed and enabled
- open
https://insiders.vscode.dev/github/microsoft/vscode-uri
- show output > anycode
- make sure there is a message like
[CONFIG] ignoring typescript because it is SUPPRESSED by any of [vscode.typescript-language-features]
. This means that anycode doesn't do anything for TS because the real TypeScript extension is there - open settings.json and paste the config below
- check that the anycode-output shows
[index] initializing index for 7 files.
- open
src/charCode.ts
- check that the anycode-output contains
[index] unleashed files matching: ts
- trigger workspace symbol search, search for
parse
, and make sure that there is a match forsrc/uri.ts#Uri.parse
// explicitly enable anycode for TS
"[typescript]": {
"anycode.language.features": {
"completions": true,
"definitions": true,
"references": true,
"highlights": true,
"outline": true,
"workspaceSymbols": true,
"folding": false,
"diagnostics": false
}
}