eclipse-lsp4e / eclipse-lsp4e/lsp4e

Add diagnostics code and URL columns to problems view and markers view

Open
#1,070 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Java
Stars
85
Forks
69
Avg merge
8h 33m
Merged PRs (30d)
6

Description

I'd like to make diagnostics details like a problem marker's problem identifier (code) and a URL to the detailed problem description visible / accessible in the problems view and in the markers view.

As soon as the issue https://github.com/eclipse-platform/eclipse.platform.ui/issues/2193 is fixed, we should adapt LSP4E to use marker content generator extensions to add new marker fields "Code" and "Details URL" to the existing problems view and to the markers view. A user will then be able to show or hide each of these marker fields in the views based on her demands. Language server providers like CDT LSP will then be able to add diagnostics details, for example, from clang-tidy like readability-magic-numbers and https://clang.llvm.org/extra/clang-tidy/checks/readability/magic-numbers.html.

This feature request is related to issue #185 and PR #1066.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review the dependency issue #2193, then inspect the existing problems view and markers view integration and the marker content generator extension approach described in the issue. Use related issue #185 and PR #1066 for context. Done means both views expose optional Code and Details URL fields that language server providers can populate.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
devtools
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.