-
Notifications
You must be signed in to change notification settings - Fork 235
Do not set breakpoint on non-PowerShell files #575
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not set breakpoint on non-PowerShell files #575
Conversation
@@ -490,7 +490,12 @@ protected void Stop() | |||
// VSCode sends breakpoint requests with the original filename that doesn't exist anymore. | |||
try | |||
{ | |||
scriptFile = editorSession.Workspace.GetFile(setBreakpointsParams.Source.Path); | |||
// When you set a breakpoint in the right pane of a Git diff window on a PS1 file, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we're checking for this prefix in another place, maybe it's time to pull this out into a helper method?
Good idea. Any suggestions on where this centralized check should be? |
BTW I'm pretty sure the test errors are because we set line breakpoints in tests with a filename of |
I think you could add a static method to ScriptFile for that. Ouch, we shouldn't be sending empty strings for paths in those tests... |
Yeah, that was probably me ... those chickens have come home to roost. :-/ I will try to finish this PR up tonight - add that static method. |
OMG, the Travis build is taking forever to start. |
Fix #574
There's still an associated but separate bug when a user is attempting to start debug on the current file when the active window is a Git diff window. I opened an issue on vscode-debugadpter-node project: microsoft/vscode-debugadapter-node#134