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

Allow query results view to act as a panel

Open
#618 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
25/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools

Research direction

Review the current query results editor webview and the linked VS Code webview views guidance. Decide whether results should be toggleable between an editor pane and a sidebar or panel, or live in the panel permanently. Done means query results render in the selected location without the editor-placement problems described.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.
Currently, our query results view is an editor webview, which consigns it to one of the editor panes. Occasionally, I find that shifting focus to and from it interacts with where VS code will place newly created editor windows, which can be annoying and unpredictable.

This also represents a potentially suboptimal use of screen real estate: In normal CodeQL development, the panel can be used to examine query logs, but often it is not part of the action; being able to use it for query results would free up more space for source code.

Describe the solution you'd like
With the advent of webview views, extensions can contribute general webview-based UIs to the side bar and panels. The highest amount of flexibility would be afforded if we could toggle between the results being displayed in an editor pane and a side bar/panel tab.

I actually think making it live in the panel permanently would be the more natural choice, but I could imagine others being less convinced.

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.