"Continue" is highlighted as a statement/keyword when used as a parameter value

Open

#224 opened on Apr 22, 2026 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 3/5
Estimated time: 1-2 days
Newbie friendliness: 55/100

Issue type: Bug
Clarity: Mostly clear
Activity status: Quiet
Tech stack: powershell, vscode
Domain: tooling

Research direction

Reproduce the issue in Visual Studio Code 1.117.0 with the PowerShell language selected, using a parameter value of "Continue". Trace the syntax-highlighting rules for parameter values and keyword recognition; done when "Continue" is highlighted like other parameter values without regressing keyword highlighting.

Written by the indexing model from the issue text.

Description

Prerequisites

Write a descriptive title.
Make sure you are able to repro it on the latest version
Search the existing issues.

Steps to reproduce

Create a new file in Visual Studio Code and select PowerShell as the language.
Call a function/cmdlet where one of the parameter values is a keyword, e.g. "Continue".

Expected behavior

Continue is highlighted in white, like other parameter values.

Actual behavior

Continue is highlighted in purple, likely meaning it is being recognized as the continue keyword.

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.6.1
PSEdition                      Core
GitCommitId                    7.6.1
OS                             Microsoft Windows 10.0.26200
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.4
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Version

Version used in Visual Studio Code 1.117.0

Visuals

No response

Dominant language: PowerShell
Stars: 151
Forks: 55
PR merge metrics: No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug]: classify_items.py cron script never includes its own required JSON schema in the prompt Open

comp/cron P2 sweeper:risk-automation type/bug

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

NousResearch/hermes-agent#117792 · 1 comment · Opened Sep 21, 2026
[Bug]: examples/custom_parser_example.py fails on Windows (hardcoded /tmp path) Open

Difficulty 2/5 1-3 hours Newbie friendliness 88/100

bancolombia/sentinel#20 · Opened Sep 20, 2026
[optimization:agents-md-curator] AGENTS.md: compress duplicated Debugging & Logging section and merge redundant autopilot rules Open

optimization optimization:agents-md-curator

Difficulty 2/5 1-3 hours Newbie friendliness 86/100

githubnext/gh-aw-cao#13143 · Opened Sep 20, 2026
Editor.navigateToCode silently does nothing when the project path contains a space Open

Difficulty 2/5 1-3 hours Newbie friendliness 82/100

flutter/dart-intellij-third-party#682 · Opened Sep 20, 2026
Rng accepts readonly arrays so callers stop copying twice Open

chore

Difficulty 2/5 1-3 hours Newbie friendliness 85/100

alunduil/woodland-generators#669 · Opened Sep 20, 2026

More DevTools issues