fix: Expose related information diagnostics#13695
Draft
wvhulle wants to merge 2 commits into
Draft
Conversation
Pulls these LSP types into their own prelude-friendly modules so downstream code (linters, widget bridges) can depend on them without importing the full Diagnostics module.
wvhulle
changed the title
github-actions
Bot
added
the
toolchain-available
|
Mathlib CI status (docs):
|
Collaborator
|
Reference manual CI status:
|
Add two optional fields to BaseMessage so message producers can attach LSP `Diagnostic.relatedInformation` items and a JSON-encoded `Diagnostic.data?` payload (consumed by the diagnostic-hover infrastructure).
wvhulle
force-pushed
the
expose-related-information-diagnostics
branch
from
66b3a8e to
b02992f
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR exposes the
relatedInformationfield standardized in the official LSP protocol to users outside of Lean core. This allows users to implement Lean linters that show additional labels in editors besides the main diagnostic.