You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a proposal to implement completionItem/resolve in order to improve the speed of completions; the need to resolve documentation dynamically was confirmed by profiling in #826.
The idea is that the textDocument/completion sends only the properties which are cheap to compute (say label, sortText, insertText, etc), while documentation, detail (and any other property since LSP 3.16.0) would be only sent once the clients requests to resolve the details with the completionItem/resolve request. This improves the initial speed and gives the user all information - no compromise.
The lag for completionItem/resolve can be lower than the perception threshold (dozens of milliseconds), and the client can pre-fetch a few completionItem/resolve as soon as it gets the completion result (I implemented this in my client here).
Would any of the maintainers be interested in accepting a PR that would do that? Any design suggestions?
I am opening this issue before starting any work as I see multiple PR hanging without response. Do I understand that this repository is now maintained by volunteers and not by the palantir anymore?
The text was updated successfully, but these errors were encountered:
Do I understand that this repository is now maintained by volunteers and not by the palantir anymore?
It's been maintained by the Spyder team since a year and a half ago. However, sometimes we've got busy with other things and don't have time to merge work here.
This is a proposal to implement
completionItem/resolve
in order to improve the speed of completions; the need to resolvedocumentation
dynamically was confirmed by profiling in #826.The idea is that the
textDocument/completion
sends only the properties which are cheap to compute (saylabel
,sortText
,insertText
, etc), whiledocumentation
,detail
(and any other property since LSP 3.16.0) would be only sent once the clients requests to resolve the details with thecompletionItem/resolve
request. This improves the initial speed and gives the user all information - no compromise.The lag for
completionItem/resolve
can be lower than the perception threshold (dozens of milliseconds), and the client can pre-fetch a fewcompletionItem/resolve
as soon as it gets the completion result (I implemented this in my client here).Would any of the maintainers be interested in accepting a PR that would do that? Any design suggestions?
I am opening this issue before starting any work as I see multiple PR hanging without response. Do I understand that this repository is now maintained by volunteers and not by the palantir anymore?
The text was updated successfully, but these errors were encountered: