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

fix: align DiagnosticRelatedInformation with the LSP spec #320

Merged
merged 1 commit into from
Apr 12, 2022

Conversation

ckipp01
Copy link
Member

@ckipp01 ckipp01 commented Apr 9, 2022

Previously this was a single DiagnosticRelatedInformation that was
possible to be attached to a diagnostic. This change aligns it with the
LSP spec
making this a List[DiagnosticRelatedInformation] instead.

Partly addresses #319

Previously this was a single DiagnosticRelatedInformation that was
possible to be attached to a diagnostic. This change aligns it with the
[LSP
spec](https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#diagnostic)
making this a `List[DiagnosticRelatedInformation]` instead.
@jastice jastice self-assigned this Apr 9, 2022
@jastice
Copy link
Member

jastice commented Apr 11, 2022

@adpi2 do you see any compatibility implications?

Copy link
Member

@adpi2 adpi2 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@adpi2 do you see any compatibility implications?

I found no Scala open source tool that currently depends on relatedInformation. I checked Metals, Bloop, sbt and Mill.

Whether there are other tools out there that uses BSP, I don't know. If there are, chances are they don't use relatedInformation neither. So I am okay to break the compatibility here.

@jastice jastice merged commit b5d2177 into build-server-protocol:master Apr 12, 2022
@ckipp01 ckipp01 deleted the relatedInforamtion branch April 12, 2022 13:40
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.

4 participants