Skip to content

Spec: structured output for WinGet CLI - #6534

Draft
Przemysław Kłys (PrzemyslawKlys) wants to merge 2 commits into
microsoft:masterfrom
PrzemyslawKlys:docs/structured-output-spec
Draft

Przemysław Kłys (PrzemyslawKlys) wants to merge 2 commits into
microsoft:masterfrom
PrzemyslawKlys:docs/structured-output-spec

Conversation

@PrzemyslawKlys

@PrzemyslawKlys Przemysław Kłys (PrzemyslawKlys) commented Sep 19, 2026

Copy link
Copy Markdown

Description

I put the JSON output proposal into a spec so we can agree on the contract before expanding the implementation in #6346.

It covers the first list and listing-only upgrade slice, the relationship to the PowerShell package object, empty and error output, and how this can live in the reporter rather than in command-specific branches. I called out the choices that still need review, especially field casing, available-version semantics, and startup failures.

This is a draft for design review. It does not add --format json or close the tracking issue.

Related Issues

Checklist

Microsoft Reviewers: Open in CodeFlow

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
There may be pipelines that require an authorized user to comment /azp run to run.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant