Get-InstalledPSResource should be Get-PSResource

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.

Steps to reproduce

Creating this issue because my comment was not addressed in #919 about Get-PSResource rename to include Installed.

Latest MS reasoning https://github.com/PowerShell/PowerShellGet/issues/919#issuecomment-1419636861:

We had an internal discussion about this, and want to make it analogous to V2 cmdlets where we have Get-InstalledModule (from the PSGet side) and Get-Module (from PowerShell side) and reduce confusion between their different outputs. Get-InstalledModule (and in V3 Get-InstalledPSResource) would get resources installed via PowerShellGet on your machine, not all of them as Get-Module does. We will also look into an alias for the command.

My comment https://github.com/PowerShell/PowerShellGet/issues/919#issuecomment-1419871881

There is no overlap/confusion between Get-Module and Get-PSResource because the noun has changed to PSResource. So why are we trying to keep the v2 convention with “Installed” as a prefix? I’m trying to understand the reasoning as “Installed” is redundant as it’s already implied that it’s installed on the system with the Get verb. If it wasn’t already installed or locally present on the system then it would have a different verb.

Issue #919 and PR #1071.

I would like to know why the team thinks there will be added value by adding Installed when the noun is PSResource not Module which was the issue with v2.

Expected behavior

Get-PSResource

Actual behavior

Get-InstalledPSResource

Error details

No response

Environment data

7.4-preview3
beta21

Visuals

No response

[ThomasNieto]

@SydneyhSmith can we get an update on why MS thinks adding Installed as a prefix creates value to Get-PSResource? In my comment rebutting the change had others like @Jaykul agreeing with me.

Here are some other points as well:

• Longer cmdlet names creates user experience difficulties especially with those who do not use tab completion.
• Users expect modules to have the same noun for cmdlets, this breaks that convention.
• Users can no longer use *-PSResource with tab completion or Get-Command -Noun PSResource to get all the verbs associated with that noun.
• The only reason that v2 had Installed as a prefix for Get-InstalledModule is because Get-Module was already used and something else had to be used. By using Get-InstalledModule caused user confusion since the two cmdlets didn’t use the same output. This is no longer an issue because v3 uses a completely different noun PSResource. There is no user expectation that the output between Get-Module and Get-PSResource would be the same.

If there is something I’m missing please let me know but right now the pros/cons are pointing to using Get-PSResource.

[alerickson]

Resolved in #1216