"Auto correct alias" setting of PowerShell extension not working

[Nicicalu]

Issue Type: Bug

Problem

The "Auto correct alias" setting of the PowerShell extension is not working as it should. If you activate it, nothing will change.

Expected result

After typing an alias, the extension should switch it out with the correct expanded Cmdlet. It should do the same as the shortcut Shift + Alt + E.

Actual result

Nothing happens. The aliases are still reported as problems and are not being replaces with the correct expanded Cmdlet.

Environment Information

Visual Studio Code

Name	Version
Operating System	Windows_NT x64 10.0.17134
VSCode	1.43.2
PowerShell Extension Version	2020.3.0

PowerShell Information

Name	Value
PSVersion	5.1.17134.858
PSEdition	Desktop
PSCompatibleVersions	1.0 2.0 3.0 4.0 5.0 5.1.17134.858
BuildVersion	10.0.17134.858
CLRVersion	4.0.30319.42000
WSManStackVersion	3.0
PSRemotingProtocolVersion	2.3
SerializationVersion	1.1.0.1

Visual Studio Code Extensions

Visual Studio Code Extensions(Click to Expand)

Extension	Author	Version
powershell	ms-vscode	2020.3.0
vscode-html-css	ecmel	0.2.3

[TylerLeonhardt]

Thanks for the info! @Nicicalu, which aliases did you see not change and can you please also attach the logs here so we can get a better idea of what's going on?

[Nicicalu]

No aliases changed and in the logs you can't see anything because nothing happenes 👎

[TylerLeonhardt]

I need the language server payload logs. Those will have important information.

This issue is being closed as inactive, if this issue is still occurring it will be re-opened

[PCAssistSoftware]

I am having this issue still - has it been fixed?

For example typing

measure -distance

would expect it to expand it to Measure-Distance -distance

?

[corbob]

I am having this issue still - has it been fixed?

For example typing

measure -distance

would expect it to expand it to Measure-Distance -distance

?

@wingers999 It looks like Tyler was waiting for payload logs, and so the bot closed it 9 months ago. Likely the issue still persists, but no information on how or when it happens means it can't really be investigated. If you're able to consistently repro it, I'd recommend opening a new issue and including the payload logs along with all the other logs.