You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Writing cross-platform and web cabable extensions, one is unable to call DebugSession::setDebuggerPathFormat and rely on the conversion methods for client and debugger path conversion.
Expected behavior
DebugSession::convertClientPathToDebugger and DebugSession::convertDebuggerPathToClient should work in desktop and web extensions.
This is a workaround for windows which doesn't play well with URIs. The
DAP
`setDebuggerPathFormat`/`convertClientPathToDebugger`/`convertDebuggerPathToClient`
can't be used as there is a [bug requiring
nodejs](microsoft/vscode-debugadapter-node#298)
which prevents usage in web extensions. Once the bug is fixed we can
update the debugger to use URIs without this PR's retry conversion.
This PR also fixes an issue where if the user closed the file being
debugged or it was open as 'temporarily open' then we couldn't step back
into the code.
Writing cross-platform and web cabable extensions, one is unable to call
DebugSession::setDebuggerPathFormat
and rely on the conversion methods for client and debugger path conversion.Expected behavior
DebugSession::convertClientPathToDebugger
andDebugSession::convertDebuggerPathToClient
should work in desktop and web extensions.Current behavior
Calling
DebugSession::convertClientPathToDebugger
orDebugSession::convertDebuggerPathToClient
throws an exceptionprocess is not defined
whenDebugSession::path2uri
andDebugSession::uri2path
are called due to a dependency onprocess.platform
fromnode
.The text was updated successfully, but these errors were encountered: