default debugger configuration "PowerShell Launch Script" doesn't work

[peetrike]

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

When creating VS Code Debugger configuration, using precreated configuration PowerShell: Launch Script, it doesn't work right after creating. The problem is with attribute script: it has just a comment about what it could be.

Instead it could use input variable that would prompt for script name to launch.

PowerShell Version

PS Version: 7.3.6

Visual Studio Code Version

PS ❯ code --version
1.80.1
74f6148eb9ea00507ec113ec51c489d6ffb4b771
x64

Extension Version

PS ❯ code --list-extensions --show-versions | select-string powershell

ms-vscode.powershell@2023.6.0

Steps to Reproduce

add configuration to debugger. It will add:

{
  "name": "PowerShell Launch Script",
  "type": "PowerShell",
  "request": "launch",
  "script": "enter path or command to execute e.g.: ${workspaceFolder}/src/foo.ps1 or Invoke-Pester",
  "cwd": "${cwd}"
},

Visuals

No response

Logs

No response

[peetrike]

it seems that the same configuration is discussed in #2995

[andyleejordan]

It is a provided default meant to be configured. If you want a "click and run" experience you can just use the triangular "play" button on a PowerShell editor in VS Code, that will launch the script in the current file (also F5 will do it).

[peetrike]

If it's a custom command template, then it would have some sort of comment included and a different name (like "PowerShell Launch Custom Command" or something similar). Then the intention of this configuration would be more obvious.

[github-actions]

This issue has been labeled as resolved, please verify the provided fix (or other reason).

[github-actions]

This issue has been labeled as needing fix verification and has not had any activity a week. It has been closed for housekeeping purposes.