Debugger is now activated when breakpoints are hit in Integrated Console #757
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change adds new behavior which causes VS Code's debugger UI to be activated when a breakpoint is hit in the Integrated Console while not currently in debug mode. This allows the user to set breakpoints and run scripts from the console while still leveraging VS Code's rich debugging UI. Resolves PowerShell#619.
|
Related to PowerShell/PowerShellEditorServices#455 |
|
Surprisingly little code change on this side. Nice! |
|
Yep! It was pretty easy to get working thankfully. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change adds new behavior which causes VS Code's debugger UI to be
activated when a breakpoint is hit in the Integrated Console while not
currently in debug mode. This allows the user to set breakpoints and
run scripts from the console while still leveraging VS Code's rich
debugging UI.
Resolves #619.