| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
|
Kirk Munro (@KirkMunro) At first look there is a lot of style changes in the PR. Could you please move them in another PR? It would be nice for code review. |
Sorry, something went wrong.
Ilya (@iSazonov) I would rather not, unless I absolutely have to. This PR was originally part of #10189, which they asked to be broken up into other PRs. After a side discussion between TylerLeonhardt, Paul Higinbotham (@PaulHigin) and Steve Lee (@SteveL-MSFT), they suggested this set of changes (adding the -Runspace parameter and refactoring under the base classes) as the second phase of the #10189 changes in an email. The only real "style changes" are replacement of cmdlet parameter property/field pairs with just properties, using static strings where appropriate (for parameter set names), and adding regions to make the set of breakpoint cmdlet classes consistent with one another. They were made while setting up base classes for the breakpoint cmdlets, which makes the code much easier to maintain going forward. I don't think they should really get in the way of this code review. |
Sorry, something went wrong.
|
Kirk Munro (@KirkMunro) I only want to speed up a code review of the PR. It is possible for reviewer to check up to 500 lines of code at a time. The PR has over 1000 changes. Also style changes distract and slows down code review too. |
Sorry, something went wrong.
The end result of the refactoring is leaner, consistent, better defined, DRY code that is easier to work with and maintain going forward. In this case, I don't believe separating some of the changes out into a separate PR buys us anything except for more work all around. |
Sorry, something went wrong.
|
Paul Higinbotham (@PaulHigin) Can you have a look at this? |
Sorry, something went wrong.
There was a problem hiding this comment.
I am not sure if this is the right direction to take for managing breakpoints in arbitrary runspaces. This has pretty big impact and so I feel there should be a formal design and sign-off before implementation. I'll add a committee review tag to get their opinion.
Sorry, something went wrong.
|
This pull request has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 15 days. It will be closed if no further activity occurs within 10 days of this comment. |
Sorry, something went wrong.
|
Aditya Patwardhan (@adityapatwardhan) and Paul Higinbotham (@PaulHigin): I have merged in master and resolved all conflicts. The single Codacy issue is incorrect, suggesting I should make a method static that cannot be made static. The PowerShell-CI-macos failures seem to have nothing to do with this PR. I have also manually re-reviewed the code changes to ensure that nothing unexpected came from the merge. From my perspective, this PR is good to go. |
Sorry, something went wrong.
|
Paul Higinbotham (@PaulHigin) Please re-review the PR. Kirk Munro (@KirkMunro) Thanks for the updates |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
Kirk Munro (@KirkMunro) Please open new issue in PowerShell-Docs repository. |
Sorry, something went wrong.
|
This pull request has been automatically marked as Review Needed because it has been there has not been any activity for 7 days. |
Sorry, something went wrong.
|
Ilya (@iSazonov): Docs issue filed, and this PR has been updated with the link at the top, so it should be good to go. |
Sorry, something went wrong.
|
Kirk Munro (@KirkMunro) Please resolve the merge conflict. |
Sorry, something went wrong.
Sorry, something went wrong.
|
Kirk Munro (@KirkMunro) Thank you for your contribution and your patience! |
Sorry, something went wrong.
|
🎉v7.1.0-preview.6 has been released which incorporates this pull request.:tada: Handy links: |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
PR Summary
PR Context
Now that the SDK has been enhanced to support breakpoint management in runspaces (see PR #10338), this PR builds on that work, exposing a common -Runspace parameter in all *-PSBreakpoint cmdlets so that users can use the same cmdlets to manage breakpoints in their local session or in a remote runspace.
PR Checklist