Include diagnostic ranges in VS Code MCP code checker#665
Open
Viktor-Gostyaikin wants to merge 1 commit into
Open
Include diagnostic ranges in VS Code MCP code checker#665Viktor-Gostyaikin wants to merge 1 commit into
Viktor-Gostyaikin wants to merge 1 commit into
Conversation
Author
Author
|
@microsoft-github-policy-service agree |
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
1 participant
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.
Summary
Extends the VS Code MCP
code_checkertool output with diagnostic location metadata.The tool already reads diagnostics through
vscode.languages.getDiagnostics(), but previously returned only severity, message, and source. This change preserves range and code metadata so MCP clients can navigate to the exact diagnostic location.Changes
startLineNumberstartColumnendLineNumberendColumndiag.codetagsrelatedInformationwith URI and range metadataMotivation
External MCP clients and coding agents need file coordinates to act on diagnostics reliably. Without ranges, diagnostics with repeated messages are ambiguous in large files.
Testing
code_checkeroutput includes diagnostic ranges.