feat: preserve LSP Diagnostic.data in markers #16766
Open
+13
−2
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.
What it does
Implemented conversion for the data field in the diagnostic <-> marker lifecycle by updating convertDiagnosticToMarkerData and reviveMarker, enabling ProblemManager markers to carry the data payload. The data field is an opaque, server-defined payload used to attach metadata to a diagnostic and must be preserved by the client. This field is defined on the Diagnostic interface in the vscode-languageserver-protocol package as below:
How to test
Follow-ups
Breaking changes
Attribution
Review checklist
nlsservice (for details, please see the Internationalization/Localization section in the Coding Guidelines)Reminder for reviewers