Add ability to push interesting results onto a stack for future exploration

Open
#567 0 comments 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
Needs clarification
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools

Research direction

Start with the issue description and resolve its open questions about path queries, persistence across restarts, and removed databases. Then identify the extension entry points for workspace-wide result state and define tests for saving and retrieving results across queries and databases; done requires an agreed design and implementation scope.

Written by the indexing model from the issue text.

Description

Complexity: Medium enhancement VSCode

Typically, when iterating through queries, a security researcher will find a handful of interesting results. This issue is about enabling the user to save specific results so that they can be explored in more detail later.

These results should be available cross-query and cross-database. I.e. there should be a single set of saved results for the entire workspace.

A few open questions:

  1. Can we save path queries? How would that work?
  2. Should we be able to store the stack across restarts?
  3. What happens if databases are removed?
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.