| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
The "hook in output" commit hooks up the ability to send output to the original client PowerShell without needing to invoke a pipeline on the server side. |
Sorry, something went wrong.
|
PoshChan-Bot (@PoshChan) please retry PowerShell-CI-static-analysis |
Sorry, something went wrong.
|
TylerLeonhardt, I do not understand the build target(s) PowerShell-CI-static-analysis; I only allow static, windows, macos, linux, all |
Sorry, something went wrong.
|
PoshChan-Bot (@PoshChan) please retry static |
Sorry, something went wrong.
|
TylerLeonhardt, successfully started retry of PowerShell-CI-static-analysis |
Sorry, something went wrong.
|
PoshChan-Bot (@PoshChan) please retry static |
Sorry, something went wrong.
|
PoshChan-Bot (@PoshChan) please retry windows |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Steve Lee (@SteveL-MSFT) - please update your review |
Sorry, something went wrong.
|
Steve Lee (@SteveL-MSFT) - please re-review |
Sorry, something went wrong.
|
🎉v7.0.0-rc.1 has been released which incorporates this pull request.:tada: Handy links: |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
This addresses two things:
This is only added to the API surface for the PowerShell extension. In theory the breakpoint cmdlets can take advantage of this in the future.
PR Context
This will light up a scenario in the PowerShell Editor Services so that when you click to add a breakpoint, that breakpoint will be applied even if the PowerShell Integrated Console is busy running the Debug-Runspace.
PR Checklist