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

Add capability to group similar results

Open
#684 1 comment 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, vscode
Domain
devtools

Research direction

Reproduce the DTraceUnsafeIndex.ql query against the linked database, then inspect the VS Code extension's results view and Problems view entry points. Implement the proposed grouping toggle and always group displayed Problems results according to the path, alert, and other-query rules; verify that duplicate paths collapse without losing the representative result.

Written by the indexing model from the issue text.

Description

enhancement VSCode

This query https://github.com/github/securitylab/blob/main/CodeQL_Queries/cpp/XNU_DTrace_CVE-2017-13782/DTraceUnsafeIndex.ql when run on the database linked here https://github.com/github/securitylab/tree/main/CodeQL_Queries/cpp/XNU_DTrace_CVE-2017-13782 will produce results like the following:

Banners_and_Alerts_and__Extension_Development_Host__-_dtrace_c_—_vscode-codeql-starter__Workspace_

You can see that many of the paths are duplicates. It's likely that in QL4E, the results were grouped together based on the comment in the ql file:

This query has 16 results. The 16th result is the vulnerability: dtrace_isa.c:817

The suggestion is the following:

  1. Add a toggle to group similar results in the results view. Similar results are defined by:
    • For Path queries
      • message is the same
      • All path elements are the same ast node
    • For alerts queries
      • message is the same
      • alert node is the same
    • For other query types
      • All elements are equal
  2. For the "Display in problems view", always group similar results. The calculation of what is similar would be slightly different since we only show the final element of a path query.
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.