-
-
Notifications
You must be signed in to change notification settings - Fork 628
refactor(language_server): make linter independent of Backend
#10497
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
refactor(language_server): make linter independent of Backend
#10497
Conversation
How to use the Graphite Merge QueueAdd either label to this PR to merge it via the merge queue:
You must have a Graphite account in order to use the merge queue. Sign up using this link. An organization admin has enabled the Graphite Merge Queue in this repository. Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue. This stack of pull requests is managed by Graphite. Learn more about stacking. |
CodSpeed Instrumentation Performance ReportMerging #10497 will not alter performanceComparing Summary
|
73faf0d
to
1a46000
Compare
6123ff4
to
a3d554d
Compare
Backend
ebafe04
to
246d6dc
Compare
a3d554d
to
ef3d0b1
Compare
246d6dc
to
db05a15
Compare
ef3d0b1
to
94f0d9d
Compare
94f0d9d
to
224d614
Compare
327d41f
to
31b5867
Compare
31b5867
to
5e67e03
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I need to get a better handle on the language server protocol, but I think this makes sense
Merge activity
|
This PR will refactor the language server, so the Linter is independent of the language server. The changes are needed to support multiple workspaces in the upstream PR. There, every linter will get its own root Uri, and will report back to the `Backend`. The `Backend` collects the different outputs from the workers and return them to the client when needed.
5e67e03
to
f6c6969
Compare
This PR will refactor the language server, so the Linter is independent of the language server.
The changes are needed to support multiple workspaces in the upstream PR.
There, every linter will get its own root Uri, and will report back to the
Backend
.The
Backend
collects the different outputs from the workers and return them to the client when needed.