René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Path Mapping on Attach request","articleBody":"### Prerequisites\n\n- [x] I have written a descriptive issue title.\n- [x] I have searched all [issues](https://github.com/PowerShell/PowerShellEditorServices/issues?q=is%3Aissue) to ensure it has not already been requested.\n\n### Summary\n\nWhen debugging a remote runspace the current logic is for PSES to retrieve back a temporary file of anything hit in a breakpoint and display it VSCode. This can be prone to some bugs and makes debugging a runspace that is not local a lot more difficult than it has to be.\n\nOther languages work around this issue by offering an option to map local path(s) to their remote equivalent and vice versa.\n\nFor example .NET's DAP launch configuration has an option called [sourceFileMap](https://code.visualstudio.com/docs/csharp/debugger-settings#_source-file-map). You can do something like\n\n```json\n{\n    \"sourceFileMap\": {\n        \"C:\\\\remote\\\\path\": \"/home/local/path\"\n    }\n}\n```\n\nPython is similar but calls the option [pathMappings](https://code.visualstudio.com/docs/python/debugging#_remote-script-debugging-with-ssh) and uses a different structure. For example:\n\n```json\n{\n    \"pathMappings\": [\n        {\n            \"localRoot\": \"/home/local/path\",\n            \"remoteRoot\": \"C:\\\\remote\\\\path\"\n        }\n    ]\n}\n```\n\nI would like to extend the attach request in PSES to support a way to map these local \u003c-\u003e remote paths so we can avoid all the psedit and file copying problems.\n\n### Proposed Design\n\nI'm more in favour of the `pathMappings` option that Python uses as the C# one is more geared around to source compilation paths than actual local/remote translations. It is slightly more verbose but it is easier to see what is the local and what is the remote.\n\nAs for the implementation there are a few locations that need to do the translation:\n\n+ [SetLineBreakpointsAsync](https://github.com/PowerShell/PowerShellEditorServices/blob/6bb322ec2150ed341991ffc7db7180db7a49539d/src/PowerShellEditorServices/Services/DebugAdapter/DebugService.cs#L129-L173) when translating the local to remote breakpoint path\n+ [FetchStackFramesAsync](https://github.com/PowerShell/PowerShellEditorServices/blob/6bb322ec2150ed341991ffc7db7180db7a49539d/src/PowerShellEditorServices/Services/DebugAdapter/DebugService.cs#L779-L892) when translating the remote stack frame file path to local\n+ [StackTraceHandler.Handle](https://github.com/PowerShell/PowerShellEditorServices/blob/6bb322ec2150ed341991ffc7db7180db7a49539d/src/PowerShellEditorServices/Services/DebugAdapter/Handlers/StackTraceHandler.cs#L38-L41) needs to update the breakpoint label\n\nThere may be others but I've not yet come across them. The option, if set, should also override the psedit mapping logic as well. Essentially it will treat the paths as local and just translate it to/from the remote paths when needed.","author":{"url":"https://github.com/jborean93","@type":"Person","name":"jborean93"},"datePublished":"2025-07-23T03:42:34.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/2242/PowerShellEditorServices/issues/2242"}