Fix #2555: Should-BeNull treats empty pipeline input as null#2689
Closed
nohwnd wants to merge 1 commit into
Closed
Fix #2555: Should-BeNull treats empty pipeline input as null#2689nohwnd wants to merge 1 commit into
nohwnd wants to merge 1 commit into
Conversation
When a function returns no output and the result is piped to Should-BeNull, PowerShell sends an empty array through the pipeline. Should-BeNull now recognizes this as no output and treats it as null. - Pipeline empty array: passes (void function output) - Explicit parameter empty array: still fails Copilot-generated fix. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
This was referenced Apr 3, 2026
Member
Author
|
Superseded by PR 2708, which fixes the same issue at the right layer: With #2708 merged, the patch on |
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.
Fix #2555
When a function returns no output and the result is piped to Should-BeNull, PowerShell sends an empty array through the pipeline. Should-BeNull now recognizes this as no output and treats it as null.
Copilot-generated fix.
Co-authored-by: Copilot 223556219+Copilot@users.noreply.github.com