Report lint/breaking check results as DiagnosticSeverityWarning in LSP#3710
Merged
Report lint/breaking check results as DiagnosticSeverityWarning in LSP#3710
DiagnosticSeverityWarning in LSP#3710Conversation
Contributor
|
The latest Buf updates on your PR. Results from workflow Buf CI / buf (pull_request).
|
emcfarlane
approved these changes
Mar 25, 2025
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 changes the severity of the lint and breaking changes to
DiagnosticSeverityWarning.Checked a couple of reference implementations (e.g. gopls, rust-analyzer), surfacing lint/breaking
file annotations as "warning" level diagnostics is reasonable. We may want to make this configurable
in the future.
Fixes #3701, this would allow format to run with lint/breaking results.
We still want to continue blocking formatting with an invalid AST.