mirror of
https://github.com/rust-lang/rust-analyzer.git
synced 2025-10-22 00:01:53 +00:00
![bors[bot]](/assets/img/avatar_default.png)
4145: Remove dead code r=matklad a=matklad
bors r+
🤖
Co-authored-by: Aleksey Kladov <aleksey.kladov@gmail.com>
54 lines
2.1 KiB
TypeScript
54 lines
2.1 KiB
TypeScript
import * as lc from 'vscode-languageclient';
|
|
import * as vscode from 'vscode';
|
|
|
|
import { CallHierarchyFeature } from 'vscode-languageclient/lib/callHierarchy.proposed';
|
|
import { SemanticTokensFeature, DocumentSemanticsTokensSignature } from 'vscode-languageclient/lib/semanticTokens.proposed';
|
|
|
|
export function createClient(serverPath: string, cwd: string): lc.LanguageClient {
|
|
// '.' Is the fallback if no folder is open
|
|
// TODO?: Workspace folders support Uri's (eg: file://test.txt).
|
|
// It might be a good idea to test if the uri points to a file.
|
|
|
|
const run: lc.Executable = {
|
|
command: serverPath,
|
|
options: { cwd },
|
|
};
|
|
const serverOptions: lc.ServerOptions = {
|
|
run,
|
|
debug: run,
|
|
};
|
|
const traceOutputChannel = vscode.window.createOutputChannel(
|
|
'Rust Analyzer Language Server Trace',
|
|
);
|
|
|
|
const clientOptions: lc.LanguageClientOptions = {
|
|
documentSelector: [{ scheme: 'file', language: 'rust' }],
|
|
initializationOptions: vscode.workspace.getConfiguration("rust-analyzer"),
|
|
traceOutputChannel,
|
|
middleware: {
|
|
// Workaround for https://github.com/microsoft/vscode-languageserver-node/issues/576
|
|
async provideDocumentSemanticTokens(document: vscode.TextDocument, token: vscode.CancellationToken, next: DocumentSemanticsTokensSignature) {
|
|
const res = await next(document, token);
|
|
if (res === undefined) throw new Error('busy');
|
|
return res;
|
|
}
|
|
} as any
|
|
};
|
|
|
|
const res = new lc.LanguageClient(
|
|
'rust-analyzer',
|
|
'Rust Analyzer Language Server',
|
|
serverOptions,
|
|
clientOptions,
|
|
);
|
|
|
|
// To turn on all proposed features use: res.registerProposedFeatures();
|
|
// Here we want to enable CallHierarchyFeature and SemanticTokensFeature
|
|
// since they are available on stable.
|
|
// Note that while these features are stable in vscode their LSP protocol
|
|
// implementations are still in the "proposed" category for 3.16.
|
|
res.registerFeature(new CallHierarchyFeature(res));
|
|
res.registerFeature(new SemanticTokensFeature(res));
|
|
|
|
return res;
|
|
}
|