Skip to content
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

WinGet List should only display results from a configured source when the --source argument is used #4236

Open
denelon opened this issue Mar 6, 2024 · 3 comments
Labels
Command-List Issue related to WinGet List Issue-Feature This is a feature request for the Windows Package Manager client.

Comments

@denelon
Copy link
Contributor

denelon commented Mar 6, 2024

Description of the new feature / enhancement

When I pass a source into WinGet List the results displayed should only be those available in that source.

Proposed technical implementation details

No response

@denelon denelon added Issue-Feature This is a feature request for the Windows Package Manager client. Command-List Issue related to WinGet List labels Mar 6, 2024
@microsoft-github-policy-service microsoft-github-policy-service bot added the Needs-Triage Issue need to be triaged label Mar 6, 2024

This comment was marked as off-topic.

@denelon denelon removed the Needs-Triage Issue need to be triaged label Mar 6, 2024
@jdhitsolutions
Copy link

I just updated to module v 1.7.10661 and can confirm this bug. If I run Get-WingetPackage -source winget I expect to see only winget sourced packages, but I see everything. I can run get-wingetpackage | where source -EQ 'winget', but I would prefer an early filtering option if available.

@denelon denelon changed the title WinGet List should only display results from a configured source with the --source argument is used WinGet List should only display results from a configured source when the --source argument is used Mar 8, 2024
fdncred pushed a commit to nushell/nu_scripts that referenced this issue Apr 23, 2024
Here is a bunch of fixes I implemented to make Winget custom completion
script functional.
Namely,
- Made it compatible with the latest Nushell version
- Fixed parsing of Winget show command
- Added the missing command aliases
- Implemented a workaround for the in Winget itself when filtering for a
particular package source -
microsoft/winget-cli#4236
@pa4k
Copy link

pa4k commented Jun 27, 2024

I have same issiue. Request winget ls -s winget or winget ls -s msstore gives me output of all installed apps regardless of the requested source. And not just the ones from the winget or msstore source.
I have WinGet ver.: 1.7.11261

maxim-uvarov pushed a commit to maxim-uvarov/nu_scripts_reduced_size that referenced this issue Oct 12, 2024
Here is a bunch of fixes I implemented to make Winget custom completion
script functional.
Namely,
- Made it compatible with the latest Nushell version
- Fixed parsing of Winget show command
- Added the missing command aliases
- Implemented a workaround for the in Winget itself when filtering for a
particular package source -
microsoft/winget-cli#4236
maxim-uvarov pushed a commit to maxim-uvarov/nu_scripts_reduced_size that referenced this issue Oct 13, 2024
Here is a bunch of fixes I implemented to make Winget custom completion
script functional.
Namely,
- Made it compatible with the latest Nushell version
- Fixed parsing of Winget show command
- Added the missing command aliases
- Implemented a workaround for the in Winget itself when filtering for a
particular package source -
microsoft/winget-cli#4236
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Command-List Issue related to WinGet List Issue-Feature This is a feature request for the Windows Package Manager client.
Projects
None yet
Development

No branches or pull requests

3 participants