Debug: add pathMappings option #5254
Conversation
JustinGrote
changed the title
|
Moving to ready per @jborean93 discord comment. |
There was a problem hiding this comment.
Pull Request Overview
This PR adds a new pathMappings configuration option to PowerShell debug configurations to support debugging remote PowerShell host processes. The feature enables mapping between local and remote file paths during debugging sessions.
- Adds
pathMappingsarray property to both PowerShell launch and attach debug configurations - Each path mapping consists of
localRootandremoteRootproperties for file path translation - Provides detailed descriptions for the new configuration options
| }, | ||
| "pathMappings": { | ||
| "type": "array", | ||
| "description": "Optional: An array of path mappings to use when debugging a remote PowerShell host process. Each mapping is an object with 'localRoot' and 'remoteRoot' properties. This is only used if the current integrated terminal is connected to a remote PowerShell runspace.", |
There was a problem hiding this comment.
The description for the attach configuration includes additional context about remote PowerShell runspace requirements, while the launch configuration description (line 639) omits this important detail. Consider adding consistent context to both descriptions or removing the extra detail from the attach description for consistency.
Copilot uses AI. Check for mistakes.
There was a problem hiding this comment.
Attach is always a remote runspace so is implied to always work. It is only the launch configuration that has the added caveat.
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
PR Summary
PR to add the options added in the PR PowerShell/PowerShellEditorServices#2251.
PR Checklist
Note: Tick the boxes below that apply to this pull request by putting an
xbetween the square brackets.Please mark anything not applicable to this PR
NA.WIP:to the beginning of the title and remove the prefix when the PR is ready