Skip to content

[New Feature]: Enable-WingetSetting and Disable-WingetSetting should return confirmation #6392

Description

@Trenly

Description of the new feature/enhancement

Currently, running Enable-WingetSetting LocalManifestFiles or Disable-WingetSetting LocalManifestFiles provides no output and it is not clear whether the command succeeded or not. The native commands winget settings --<Enable|Disable> LocalManifestFiles provide output that the setting was either enabled or disabled, It would provide much better feedback to the user if the PowerShell module returned the setting and its state as a confirmation that it was set

Proposed technical implementation details (optional)

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Enable-WingetSetting LocalManifestFiles
Name               Value
----               -----
LocalManifestFiles True

PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs>
PS C:\Users\WDAGUtilityAccount\Desktop\winget-pkgs> Disable-WingetSetting LocalManifestFiles
Name               Value
----               -----
LocalManifestFiles False

Metadata

Metadata

Assignees

No one assigned

    Labels

    Issue-FeatureThis is a feature request for the Windows Package Manager client.PowerShellIssue related to WinGet PowerShell Module or cmdlet

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions