-
Notifications
You must be signed in to change notification settings - Fork 148
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
Listener API #99
Comments
19 tasks
I guess we can close this one? |
Please reopen if needed! |
Oops, yes, thanks. We'll learn more as people think of things to do with
it. Probably need to expose a client-side one, too, at some point...
…On Tue, Jan 14, 2020, 18:35 Michał Krassowski ***@***.***> wrote:
Closed #99 <https://github.com/krassowski/jupyterlab-lsp/issues/99>.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/krassowski/jupyterlab-lsp/issues/99?email_source=notifications&email_token=AAALCRG3DWEHHOPVRN4TTSDQ5ZD2RA5CNFSM4JKAO3LKYY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOV7DCRHQ#event-2948999326>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAALCRENQTZCFZNFGKUBMN3Q5ZD2RANCNFSM4JKAO3LA>
.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A number of issues (#95, #17, probably more) have identified a need for writing
concrete files to disk in order for language servers to act on them. This is
sufficient to start the conversation about allowing the pipeline of language
messages to be intercepted by any number of agents. Currently the flow looks like:
Proposed is to allow any number of listeners to react to the messages.
Not proposed is to actually change or prevent the delivery of messages,
nor to encourage direct access to the handlers or servers, but rather to delay
delivery of a message until some external side effect has been completed, in the
initial case, the writing of a file to disk.
This particular case could be achieved through direct use of the existing
ContentsManager
API, but in this case, LSP provides a change-based approachover WebSockets that is likely more performant.
notional API
As these cannot change the message, they can be scheduled to run in "parallel".
notional manager changes
The text was updated successfully, but these errors were encountered: