Produce machine-readable output from `choco install --noop --limit-output`
- Dominant language
- C#
- Stars
- 11.5k
- Forks
- 960
- PR merge metrics
- No merged PRs in 30d
Description
Currently (0.10.0), `--limit-output` has little effect on `choco install --noop` - it only suppresses the two initial lines containing Chocolatey version and command name, but the rest of output is not really suitable for machine consumption.
It would be nice if the output looked more like that of `choco list --local-only` (pipe-separated values): a symbol denoting the operation performed on the given package (I-install, U-upgrade), package id, package version, existing package version (in case of upgrade), package status, verifier status. Such as:
```
C:\>cinst netfx-4.6.2-devpack --noop -r
I|KB2919442|1.0.20160719||Approved|
I|KB2919355|1.0.20160719||Approved|broken
U|vcredist2015|14.0.24212.0|14.0.23918.0|Submitted|broken
U|chocolatey-uninstall.extension|1.1.0|1.0.0|Approved|
I|dotnetcore-runtime.install|1.0.0||Approved|broken
I|dotnetcore-runtime|1.0.0||Approved|broken
```
Contributor guide
Research direction
Start by comparing the output of `choco install --noop --limit-output` with `choco list --local-only`, focusing on the existing pipe-separated format. The work is done when noop installation output reports the requested operation, package identifiers and versions, existing versions for upgrades, package status, and verifier status in a machine-readable format.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100