Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Support viewing the intepreted results of diagnostic queries

Open
#975 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

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

Research direction

Start in the VS Code extension's existing interpreted-result display for alert and path alert queries, then compare it with the CLI's diagnostic-query summary table. Support both located and unlocated diagnostic results, including per-result severity where present; done means interpreted diagnostic results can be viewed rather than only raw results.

Written by the indexing model from the issue text.

Description

VSCode

Currently the VS Code extension supports viewing the raw results of diagnostics queries, but it can't view the interpreted results of diagnostics queries like it can for alert and path alert queries. Located diagnostics queries can likely be displayed similarly to alerts — the only difference is that results may have an associated per-result severity, as opposed to the per-query severity of alert queries. Unlocated diagnostics queries are a little more difficult to display. We may want to take inspiration here from the summary table printed by the CLI.

Dominant language
TypeScript
Stars
539
Forks
240
Avg merge
2d 6h
Merged PRs (30d)
29

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.

More from github/vscode-codeql

All issues in github/vscode-codeql

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.