1 Describe the bug
2 When using the "Open in Editor" feature, if a file's URL from the DevTools doesn't map to a local file due to a
missing or incorrect pathMapping configuration in launch.json, the error message is generic. It doesn't guide
the user on how to resolve the issue.
3
4 To Reproduce
5 Steps to reproduce the behavior:
6 1. Configure a project with an incorrect pathMapping in launch.json (e.g., map "/" to the wrong directory).
7 2. Launch the debugger and open the Edge DevTools.
8 3. In the DevTools "Elements" or "Sources" panel, click a link to a source file.
9 4. See the error message.
10
11 Expected behavior
12 The error message should be actionable, suggesting that the user inspect their pathMapping configuration in
launch.json.
13
14 Current behavior
15 A generic error appears, stating: "Could not open document. No workspace mapping was found for '[url]'."
16
17 Additional context
18 Improving this error message would significantly help users troubleshoot their configuration and reduce friction
when using the "Open in Editor" feature.