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

Add stubs for missing method overrides

Open
#636 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
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
typescript, vscode
Domain
developer-experience, devtools

Research direction

The issue names no implementation files or tests. Start by locating the VS Code extension entry point for class-related actions and the CodeQL language-service support for abstract methods; compare with how Java IDEs generate override stubs. Done means the command inserts correctly formatted stubs for every missing abstract method, including multiple abstract base classes.

Written by the indexing model from the issue text.

Description

enhancement VSCode

Is your feature request related to a problem? Please describe.

I'm always frustrated when subclassing an abstract class in QL, since I need to manually write out names and signatures of abstract methods I must implement.

And all the while, my IDE is laughing at my struggle, since it knows what I need to do (with the <YourClass> must implement abstract method: <methodName> errors).

I usually go to the abstract base class and use multiple-cursors on the abstract part, but with multiple base classes that are abstract, even this process becomes tedious.

Describe the solution you'd like

class MyClass extends AbstracClass {
  MyClass() { this = foo() }
}

Right-click the MyClass part of class MyClass, select Add stubs for missing method overrides, and the above code is extended to become

class MyClass extends AbstracClass {
  MyClass() { this = foo() }

  override string method1(int arg) { 
    // TODO: this is a stub
    none() 
  }

  override method2() {
    // TODO: this is a stub
    none() 
  }
}

I think this is very common in Java, so we might be able to borrow how the stubs are populated from there (like how the TODO comment is formulated).

Describe alternatives you've considered
N/A

Additional context
N/A

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.