Add -CaseInsensitive switch parameter to Select-Object & Get-Unique cmdlet documentation

[ArmaanMcleod]

Prerequisites

• Existing Issue: Search the existing issues for this repository. If there is an issue that fits your needs do not file a new one. Subscribe, react, or comment on that issue instead.
• Descriptive Title: Write the title for this issue as a short synopsis. If possible, provide context. For example, "Document new Get-Foo cmdlet" instead of "New cmdlet."

Summary

Added -CaseInsensitive switch parameter to Select-Object & Get-Unique cmdlets.

The Select-Object and Get-Unique cmdlets currently do case-sensitive string comparison when filtering unique items, and don't allow the user to override this behaviour and use case-insensitive comparison.

This helps users do case-insensitive string comparison when using these cmdlets.

Details

Examples

Select-Object -Unique

> "derp", "Derp" | Select-Object -Unique
derp
Derp

> "derp", "Derp" | Select-Object -Unique -CaseInsensitive
derp

Get-Unique

> "aa", "Aa", "bb", "Bb" | Get-Unique
aa
Aa
bb
Bb

> "aa", "Aa", "bb", "Bb" | Get-Unique -AsString -CaseInsensitive
aa
bb

> "aa", "Aa", "bb", "Bb" | Get-Unique -CaseInsensitive
aa
bb

Articles

• reference/7.4/Microsoft.PowerShell.Utility/Select-Object.md
• reference/7.4/Microsoft.PowerShell.Utility/Get-Unique.md

Related Source Pull Requests

• Added -CaseInsensitive switch parameter to Select-Object & Get-Unique cmdlets PowerShell/PowerShell#19683

Related Source Issues

• Select-Object -unique is inconsistently case sensitive PowerShell/PowerShell#12059