Allow users to add a whitelist to Expand-Aliases

[AdmiringWorm]

Would be useful to have the ability to add a white list of aliases that shouldn't be expanded when running Expand-Aliases.

[AdmiringWorm]

I have added this now in a local branch, and is ready to be published when the next release comes around.

/cc @majkinetor (I believe you were the one that asked for this feature some time ago?)

[majkinetor]

Removing % and ? from expanding on core ASAP.

[AdmiringWorm]

it's not available yet, and won't be either until the rest of my planned features have been implemented.

The issue was just closed since I pushed the code up to github.

[majkinetor]

I noticed.

I have it prepared: if (Test-Path tools) { Expand-Aliases -Directory tools -Whitelist '?','%','ls' } , just let me know when you push to gallery 👂

[AdmiringWorm]

While I agree adding the ? and %, but not ls as that could potentially be mapped to a executable which could break the install script for those users.

You should also add the Get-PackageParameter to the whitelist, as that have been changed to an alias in chocolatey.

[majkinetor]

It can't AFAIK. Aliases have priority over exes and ls is there among internal aliases since v0. And furthemore, Get-ChildItem vs ls is really no brainer. Not everybody is in this non alias nonsence vagon: PowerShell/PSScriptAnalyzer#214

[majkinetor]

Let me stand corrected. On linux it can and it does now. But when we arrive with chocolatey on Linux then we will think about that.