I would like input from the maintainers on whether they think an experimental feature is required in this case. I can't think of a use case where anyone would use -ExcludeDifferent without wanting to see the objects that are equal, but I can see where it could still technically be a breaking change.

@PowerShell/powershell-committee Can your review and see if we want to take this change, if it should be experimental, and if we should call it breaking?

I think it should be experimental. I think this is breaking change, bucket 2. I think someone could have reasonably taken a decency on this, but I think the new behavior is predictable and obvious.

/cc @mklement0

One of the macos failures doesn't look random. You may need to rebase. Tell me if you need me to do that for you.

@PowerShell/powershell-committee reviewed this. We agree that the original intent is that -IncludeEqual is implicit with -ExcludeDifferent otherwise -ExcludeDifferent by itself is not useful.

@davidseibel I rebased your branch to see if it resolved the failure. Be sure to pull the changes, before making any additional changes.

@PoshChan Please remind me in 1 hour

@TravisEz13 - thanks, sorry for the slow response on my part. For my own benefit, would you mind explaining how you rebased? Still learning here...

@TravisEz13, this is the reminder you requested 1 hour ago

@davidseibel probably safest to do a git reset origin/master (assuming your Github repository is your main remote) since Travis needed to force-push to do the rebase.

Check git remote -v before doing anything else if you're not sure what your remotes are, and confirm the name of your fork's github remote & sub that instead of origin if it's different.

@davidseibel Thanks for your contribution!

🎉v7.1.0-preview.3 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes