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

CodeQL model editor: Support adding additional flows to already modeled methods

Open
#3,205 1 comment 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
45/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
devtools

Research direction

No file or test is named. Start by locating the CodeQL model editor UI that renders the "Method already modeled" entry, then verify the requested behavior: show a "+" control for additional flows while keeping controls for existing flows disabled.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.
When a method is already modeled, the entry shows only "Method already modeled" and there is no way to add additional flows.
This means:

  • you can't see the details of the existing model (type, input, output, kind)
  • you can't add additional flows because there is no "+" button

Describe the solution you'd like
The "+" button should also be shown for already modeled methods.

Side notes:

  • It might also be nice if instead of "Method already modeled", it would show how the method is modeled (type, input, output, kind) to notice issues or missing flow. Possibly also with multiple lines if there are multiple flows.
    But the dropdowns and the delete button should be disabled for these existing flows.
  • When "Hide modeled methods" is unselected, it might be useful to show the modeled methods intermixed with the un-modeled methods.
    Currently they are all shown as one group at the end of that API section, so you have to jump back and forth to see if / how the methods of a class are modeled in case some are already modeled and some are not.
    (Some users might prefer the existing grouping though?)

Describe alternatives you've considered
none

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

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.