aboutsummaryrefslogtreecommitdiff
path: root/helix-term/src/ui/completion.rs
diff options
context:
space:
mode:
authorMichael Davis2022-11-18 18:27:46 +0000
committerGitHub2022-11-18 18:27:46 +0000
commit89efb4f711d37ac59b4f5f985467647be76fb870 (patch)
tree70fb86125d9ddf601fd9de16cdf88c51b2284f77 /helix-term/src/ui/completion.rs
parenteada6d534e022b66e1c1d631670dc1ccbe922b9e (diff)
lsp: Resolve completion item asynchronously on idle-timeout (#4781)
d7d0d5ffb79b6f2e09c6ab8af6e112c41e6f73e8 resolves completion items on the idle-timeout event. The `Completion::resolve_completion_item` function blocks on the LSP request though, which blocks the compositor and in turn blocks the event loop. So until the language server returns the resolved completion item, Helix is unable to respond to keypresses or other LSP messages. This is typically ok since the resolution request is fast but for some language servers this can be problematic, and ideally we shouldn't be blocking like this anyways. When receiving a `completionItem/resolve` request, the Volar server sends a `workspace/configuration` request to Helix and blocks itself on the response, leading to a deadlock. Eventually the resolve request times out within Helix but Helix is locked up and unresponsive in that window. This change resolves the completion item without blocking the compositor.
Diffstat (limited to 'helix-term/src/ui/completion.rs')
-rw-r--r--helix-term/src/ui/completion.rs48
1 files changed, 38 insertions, 10 deletions
diff --git a/helix-term/src/ui/completion.rs b/helix-term/src/ui/completion.rs
index 229dcda1..4e6ee424 100644
--- a/helix-term/src/ui/completion.rs
+++ b/helix-term/src/ui/completion.rs
@@ -257,7 +257,7 @@ impl Completion {
let future = language_server.resolve_completion_item(completion_item);
let response = helix_lsp::block_on(future);
match response {
- Ok(completion_item) => Some(completion_item),
+ Ok(value) => serde_json::from_value(value).ok(),
Err(err) => {
log::error!("execute LSP command: {}", err);
None
@@ -304,6 +304,12 @@ impl Completion {
self.popup.contents().is_empty()
}
+ fn replace_item(&mut self, old_item: lsp::CompletionItem, new_item: lsp::CompletionItem) {
+ self.popup.contents_mut().replace_option(old_item, new_item);
+ }
+
+ /// Asynchronously requests that the currently selection completion item is
+ /// resolved through LSP `completionItem/resolve`.
pub fn ensure_item_resolved(&mut self, cx: &mut commands::Context) -> bool {
// > If computing full completion items is expensive, servers can additionally provide a
// > handler for the completion item resolve request. ...
@@ -313,16 +319,38 @@ impl Completion {
// > 'completionItem/resolve' request is sent with the selected completion item as a parameter.
// > The returned completion item should have the documentation property filled in.
// https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#textDocument_completion
- match self.popup.contents_mut().selection_mut() {
- Some(item) if item.documentation.is_none() => {
- let doc = doc!(cx.editor);
- if let Some(resolved_item) = Self::resolve_completion_item(doc, item.clone()) {
- *item = resolved_item;
+ let current_item = match self.popup.contents().selection() {
+ Some(item) if item.documentation.is_none() => item.clone(),
+ _ => return false,
+ };
+
+ let language_server = match doc!(cx.editor).language_server() {
+ Some(language_server) => language_server,
+ None => return false,
+ };
+
+ // This method should not block the compositor so we handle the response asynchronously.
+ let future = language_server.resolve_completion_item(current_item.clone());
+
+ cx.callback(
+ future,
+ move |_editor, compositor, response: Option<lsp::CompletionItem>| {
+ let resolved_item = match response {
+ Some(item) => item,
+ None => return,
+ };
+
+ if let Some(completion) = &mut compositor
+ .find::<crate::ui::EditorView>()
+ .unwrap()
+ .completion
+ {
+ completion.replace_item(current_item, resolved_item);
}
- true
- }
- _ => false,
- }
+ },
+ );
+
+ true
}
}