Add -IgnoreOrder to Should-ContainCollection - #2925
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
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 #2874
Should-ContainCollectionrequires the expected items in the same order, which is annoying when migrating fromShould -BeInwhere the order did not matter. This adds an-IgnoreOrderswitch that only checks that the expected items are present, in any order.The check is a multiset subset (new internal
Is-CollectionSubset), so duplicates and$nullare handled correctly, each expected item is matched at most once. Without the switch the ordered behavior is unchanged.Added tests for the ordered and unordered cases, duplicates and
$null.🤖