Restore default PSScriptAnalyzer ruleset

[alejandro5042]

I want to use aliases, but as of today's update, I am getting underlines all over my source. They are very distracting and I cannot find a way to disable them. Is there an option? If not, I propose this being an issue that should be fixed.

[daviwil]

Apologies for that, we have changed to a different method for integration PowerShell Script Analyzer and didn't carry over the default ruleset we were using before. I'll address this in a patch release in a few days.

[daviwil]

Fixed in the latest release!

[kilasuit]

@daviwil personally i dont feel this is "fixed" as realistically the default ruleset should be to have any rules that emit warnings or errors throw - exactly as it would be if you just ran Invoke-ScriptAnalyzer -Severity Error,Warning

We then can allow users like @alejandro5042 to disable the Aliases rule using their own rulesets but for the greater good of the community and those new to PowerShell they need to be warned about the fact that aliases can break scripts.

For example I regularly see organisations deploy as part of their base OS images a $PROFILE.AllUsersAllHosts that includes

Remove-Item Alias:\* -force

would break all of @alejandro5042 scripts and is exactly why you should never use aliases.

Happy to raise this as another issue but I feel that pleasing 1 user in this case @alejandro5042 isn't in the best interests of the community especially now that it is going to start growing even bigger.

[alejandro5042]

I know I have already voiced my opinion on the other thread. I'm afraid the use of aliases is "religious" in nature and we'll only have to agree to disagree.

Remove-Item Alias:\* -force

Why should I--an unrelated user--have to support the workflow of someone who is intentionally removing all their aliases? Aliases are part of the PowerShell language and are extremely useful for day-to-day usage. I shouldn't have to pay the penalty because you don't like a built-in language feature.

For example, take this very specific, very simple command, and see how using aliases blows it up into something that's unapproachable and difficult to read.

$buildDefinitions | where TriggerType -match "GatedCheckIn" | foreach Name | sls "^R" | sort Length -desc

vs.

$buildDefinitions | Where-Object TriggerType -match "GatedCheckIn" | Foreach-Object Name | Select-String "^R" | Sort-Object Length -Descending

Now I understand, I'm primarily a C# coder and in C# we spell everything out. But I use PowerShell as a scripting environment where things should be easy and fast.

Again, we can agree to disagree.