| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM with one comment.
Sorry, something went wrong.
There was a problem hiding this comment.
LGTM
Sorry, something went wrong.
|
@PowerShell/powershell-committee the decision here is what to do about removing a workflow specific value from the existing public enum. One option is to mark it obsolete. |
Sorry, something went wrong.
|
@PowerShell/powershell-committee reviewed this, we discussed removal, using [obsolete] attribute, and leaving as-is. We discussed the possibility of using this value in the future for job control if there is a way to suspend a PSJob. For that reason, we agreed to leave this enum value. We also recommend that we explicitly number enum values so in the future, if we do decide to remove a value and add another one, then existing code will break/behavior appropriately. |
Sorry, something went wrong.
|
To address the committee review feedback, I just made the following changes:
I'll also update the OP accordingly. |
Sorry, something went wrong.
|
Note that regarding explicit numbering of the ActionPreference enumerated values, I have that handled in PR #8205. Also, once either this PR or #8205 are merged in, I will update the other PR accordingly because there are some overlapping changes that I doubt will merge without manual intervention. |
Sorry, something went wrong.
|
Just FYI in case it wasn't clear: I updated this PR once #8205 was merged into PowerShell, so this PR is one again ready for review/merge. Two of the three Codacy issues are incorrect (looks like it needs to be updated for modern syntax), and the third one is related to a Pester test and will be ignored. |
Sorry, something went wrong.
|
Paul Higinbotham (@PaulHigin) Could you please update your review (we have new commits)? |
Sorry, something went wrong.
|
FYI, I will not be making changes based on the Codacy review because one of the issues is a false positive, and the other two are incorrect. This PR is ready for review by other reviewers. |
Sorry, something went wrong.
|
Steve Lee (@SteveL-MSFT) PowerShell Committee request was addressed. Can we merge? |
Sorry, something went wrong.
…orted, reserved state, and remove restriction on using ActionPreference.Ignore in preference variables (PowerShell#10317)
|
🎉v7.0.0-preview.4 has been released which incorporates this pull request.:tada: Handy links: |
Sorry, something went wrong.
…orted, reserved state, and remove restriction on using ActionPreference.Ignore in preference variables (PowerShell#10317)
| Back | FazBrowse Home | New Git URL |
PR Summary
As part of the cleanup of workflow code, this PR does the following:
PR Context
See issue #9570.
PR Checklist