Different UX modes for WinGet

[denelon]

Description of the new feature / enhancement

Sometimes I want winget to behave as simply an "engine" for managing packages. In that case, I want commands to either succeed or fail with meaningful output because no user is at the keyboard to respond to prompts for input.

Other times, I want winget to behave more interactively, so I can have a better UX. For example, when there are multiple packages found matching a command, I don't want to have to type the entire command again, I just want an interactive prompt to save the keyboard strokes.

Related to:

• Ability to easily choose package #1830

Proposed technical implementation details

I want a setting to define the default behavior.

I want a set of arguments to override the default behavior.

Note, if this is implemented in a 1.x version of WinGet, the default behavior would be in the "engine" mode above to not break existing automation.

Otherwise, this would be considered a breaking change in behavior and would be part of:

• Breaking changes to properly justify a 2.0 release #2128

[denelon]

This is partially implemented by:

• https://github.com/microsoft/winget-cli/blob/master/schemas/JSON/settings/settings.schema.0.2.json#L172

[denelon]

We also have an argument to "--disable-interactivity" if the setting is configured to be interactive.

• Add prompts when installer aborts terminal or needs install location #1814

[denelon]

The remaining work would be:

• Add an argument for "--enable-interactivity" in the event the setting is defaulted to disabled.
• Change the default behavior in a future 2.0 release.