PowerShell / PowerShell/vscode-powershell
Conditional Breakpoint query does not work in pipeline ($_ not recognized)
Dieses Issue hat noch niemand übernommen.
- Vorherrschende Sprache
- TypeScript
- Sterne
- 1.9k
- Forks
- 548
- PR-Merge-Kennzahlen
- Keine gemergten PRs in 30 T.
Beschreibung
Prerequisites
- I have written a descriptive issue title.
- I have searched all open and closed issues to ensure it has not already been reported.
- I have read the troubleshooting guide.
- I am sure this issue is with the extension itself and does not reproduce in a standalone PowerShell instance.
- I have verified that I am using the latest version of Visual Studio Code and the PowerShell extension.
- If this is a security issue, I have read the security issue reporting guidance.
Summary
Hi there,
During PSConfEU there was a demo about VSCode and I was following along and I realized that for conditional breakpoints there seems to be a bug where $_ would not be recognized in the queries. If I would use the conditional breakpoint in a foreach loop (keyword) it would work no problem with the loop variable. The issue as far as I can see only exist in Foreach-Object within the pipeline.
PowerShell Version
PS /Users/kevinbates/Code/PSConf25> $PSVersionTable; $host
Name Value
---- -----
PSVersion 7.4.6
PSEdition Core
GitCommitId 7.4.6
OS Darwin 24.5.0 Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:25 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T6020
Platform Unix
PSCompatibleVersions {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion 2.3
SerializationVersion 1.1.0.1
WSManStackVersion 3.0
Name : Visual Studio Code Host
Version : 2025.0.0
InstanceId : 4c1c07d9-cbf8-40b2-8f41-6c2866edb05b
UI : System.Management.Automation.Internal.Host.InternalHostUserInterface
CurrentCulture : en-US
CurrentUICulture : en-US
PrivateData : Microsoft.PowerShell.ConsoleHost+ConsoleColorProxy
DebuggerEnabled : True
IsRunspacePushed : False
Runspace : System.Management.Automation.Runspaces.LocalRunspace
Visual Studio Code Version
PS /Users/kevinbates/Code/PSConf25> code --version
1.100.3
258e40fedc6cb8edf399a463ce3a9d32e7e1f6f3
arm64
Extension Version
PS /Users/kevinbates/Code/PSConf25> code --list-extensions --show-versions | select-string powershell
ms-vscode.powershell@2025.0.0
Steps to Reproduce
I can run this piece of code:
$numbers = 1..100
foreach($number in $numbers){
write-host $number
}
with the following conditional breakpoint on the line within the loop:
$number -eq 100
And the breakpoint will hit as expected. If I change up my code to use Foreach-Object. It will no longer hit.
1..100 | ForEach-Object {
write-host $_
}
with the following expression:
$_ -eq 5
Visuals
No response
Logs
No response
Beitragsleitfaden
Erste Schritte
- Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
- Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
- Forke das Repository und arbeite in einem Branch.
- Öffne einen Pull Request, der die Issue-Nummer nennt.
Rechercherichtung
Beginnen Sie damit, das Verhalten bedingter Haltepunkte in Visual Studio Code mit der PowerShell-Erweiterung zu reproduzieren, und vergleichen Sie dabei die foreach-Schleife mit dem ForEach-Object-Pipeline-Beispiel aus dem Issue. Verfolgen Sie den Einstiegspunkt der Behandlung bedingter Haltepunkte und überprüfen Sie, dass $_ -eq 5 im Pipeline-Fall die Ausführung anhält, ohne das bestehende Verhalten von $number -eq 100 zu beeinträchtigen.
Vom Indexierungsmodell aus dem Issue-Text verfasst.
Bewertung
- Tech-Stack
- powershell, typescript, vscode
- Bereich
- devtools
- Issue-Typ
- Bug
- Schwierigkeit
- 4/5
- Geschätzter Aufwand
- 3-5 Tage
- Aktivitätsstatus
- Veraltet
- Klarheit
- Größtenteils klar
- Anfängerfreundlichkeit
- 45/100