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

Highlight related keywords under cursor

Open
#5,058 1 comment 1 reaction 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
powershell, typescript, vscode
Domain
tooling

Research direction

No files, tests, or entry points are named. Start by locating the extension's existing keyword-highlighting and syntax/AST handling, then compare the requested if/else, try/catch/finally, return, and loop-flow cases, including labeled PowerShell loops; done means related keywords highlight at the cursor without incorrect matches.

Written by the indexing model from the issue text.

Description

Issue-Enhancement Up for Grabs
Prerequisites
  • I have written a descriptive issue title.
  • I have searched all issues to ensure it has not already been reported.
Summary

Some keywords relate to each other, like "break" or "continue" inside a loop statement. It would be nice if these keywords got highlighted when placing the cursor on them just like it happens in VS and VScode when writing C# code. Here's an example:
image

This makes it easier to tell at a glance which loop I'm breaking out of in a nested loop scenario.

The scenarios that C# covers from my memory are:
1: Obvious pairs (if/else, try/catch/finally)
2: Return statements inside methods
3: Loops and flow control statements

All 3 seem like they would be pretty simple to handle with some AST analysis, however because PowerShell has loop labels extra care should be taken when determining what loop the flow control statements relate to.

Proposed Design

No response

Dominant language
TypeScript
Stars
1.9k
Forks
548
PR merge metrics
No merged PRs in 30d

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 PowerShell/vscode-powershell

All issues in PowerShell/vscode-powershell

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.