mirror of
https://github.com/rust-lang/rust-analyzer
synced 2025-01-13 13:48:50 +00:00
Remove dead code
This commit is contained in:
parent
bd9ede0ec9
commit
0ac5ed5a84
1 changed files with 0 additions and 29 deletions
|
@ -42,35 +42,6 @@ export async function createClient(serverPath: string, cwd: string): Promise<lc.
|
||||||
clientOptions,
|
clientOptions,
|
||||||
);
|
);
|
||||||
|
|
||||||
// HACK: This is an awful way of filtering out the decorations notifications
|
|
||||||
// However, pending proper support, this is the most effecitve approach
|
|
||||||
// Proper support for this would entail a change to vscode-languageclient to allow not notifying on certain messages
|
|
||||||
// Or the ability to disable the serverside component of highlighting (but this means that to do tracing we need to disable hihlighting)
|
|
||||||
// This also requires considering our settings strategy, which is work which needs doing
|
|
||||||
// @ts-ignore The tracer is private to vscode-languageclient, but we need access to it to not log publishDecorations requests
|
|
||||||
res._tracer = {
|
|
||||||
log: (messageOrDataObject: string | unknown, data?: string) => {
|
|
||||||
if (typeof messageOrDataObject === 'string') {
|
|
||||||
if (
|
|
||||||
messageOrDataObject.includes(
|
|
||||||
'rust-analyzer/publishDecorations',
|
|
||||||
) ||
|
|
||||||
messageOrDataObject.includes(
|
|
||||||
'rust-analyzer/decorationsRequest',
|
|
||||||
)
|
|
||||||
) {
|
|
||||||
// Don't log publish decorations requests
|
|
||||||
} else {
|
|
||||||
// @ts-ignore This is just a utility function
|
|
||||||
res.logTrace(messageOrDataObject, data);
|
|
||||||
}
|
|
||||||
} else {
|
|
||||||
// @ts-ignore
|
|
||||||
res.logObjectTrace(messageOrDataObject);
|
|
||||||
}
|
|
||||||
},
|
|
||||||
};
|
|
||||||
|
|
||||||
// To turn on all proposed features use: res.registerProposedFeatures();
|
// To turn on all proposed features use: res.registerProposedFeatures();
|
||||||
// Here we want to enable CallHierarchyFeature and SemanticTokensFeature
|
// Here we want to enable CallHierarchyFeature and SemanticTokensFeature
|
||||||
// since they are available on stable.
|
// since they are available on stable.
|
||||||
|
|
Loading…
Reference in a new issue