Repository navigation
Honor inherited information suppression on Windows PowerShell 5.1 - #27
Merged
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
When an enclosing command uses
-InformationAction Ignore, Windows PowerShell 5.1 rejects inherited Ignore in nestedWrite-HostandWrite-Informationcalls.Write-Colornow suppresses Host and Information rendering for both direct and inherited Ignore preferences. Output and Verbose messages remain independent, file logging continues, and subsequent calls retain their normal preferences.This closes the merged-package compatibility failure found while preparing O365Synchronizer PR #55 for issue #52. It follows PSWriteColor PR #26. PSWriteColor owns stream suppression; O365Synchronizer consumes the fixed owner and requires version 1.0.7. Publish this owner release before merging and publishing the consumer.
All 48 module tests pass on Windows PowerShell 5.1 and PowerShell 7. The two new same-module nesting regressions fail against public version 1.0.6 and pass with this fix. Independent targeted confirmation found no actionable defects. The consumer's signed merged-package Windows PowerShell 5.1 verification remains a release gate after the fixed owner is published.