Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Explore how to implement isIncomplete support #838

Draft
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

krassowski
Copy link
Member

@krassowski krassowski commented Aug 23, 2022

References

Partially fixes #776 but does not work reliably; instead an implementation upstream in JupyterLab is needed. We need to think how to add this. Supporting isIncomplete is needed because:

  • it enables faster completions when latency between server is low
  • it is a non-optional part of LSP spec
  • servers like TexLab and R server depend on it for completions

Not sure if i will be merging this one (not happy with how non-reliably this works), unless I can fix it without relying on extensive changes upstream.

Also upstream: reply type for completion should be AnyCompletion | null.

TODO:

  • use TriggerForIncompleteCompletions
  • fix update issues

Code changes

User-facing changes

Backwards-incompatible changes

Chores

  • linted
  • tested
  • documented
  • changelog entry

@github-actions
Copy link

Binder 👈 Launch a binder notebook on branch krassowski/jupyterlab-lsp/fix-incomplete-completion

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

TexLab candidates not refreshed
1 participant