-
Notifications
You must be signed in to change notification settings - Fork 1.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PowerShell pipe to sort fails #2798
Comments
In case someone else finds this, the example
The ID is actually in Find-WinGetPackage terminal -Source winget | Sort { $_.CatalogPackage.Id } So really the surprising behavior comes form the ls | sort djk30f9u3f93if # short-form of: Get-ChildItem | Sort-Object -Property djk30f9u3f93if and it doesn't care. To make this less surprising for users of the Winget module though, maybe PowerShell object |
The problem is that all of the properties are buried. This is not a user-friendly experience. This is what we are discussing at #2796 |
Yes, and it is particularly interesting in the case of the
EDIT: well I can see that it makes sense from a technical standpoint, the I guess if the objects returned from |
This will be in the next preview release. |
and this:
These break from expected PowerShell behaviors.
Originally posted by @jdhitsolutions in #2796 (comment)
The text was updated successfully, but these errors were encountered: