microsoft / microsoft/knack

TSV output doesn't include headers

Open
#234 0 comments 2 reactions 1 assignee View on GitHub

@jiasli is already working on this.

Since Feb 25, 2021.

Dominant language
Python
Stars
358
Forks
101
PR merge metrics
No merged PRs in 30d

Description

Currently tsv output is the only output type that doesn't include headers, despite tsv files commonly having headers. Is there a reason to remove headers for this output type?

C:\Users\smehan>az version -o json
{
  "azure-cli": "2.9.1",
  "azure-cli-command-modules-nspkg": "2.0.3",
  "azure-cli-core": "2.9.1",
  "azure-cli-nspkg": "3.0.4",
  "azure-cli-telemetry": "1.0.4",
  "extensions": {
    "azure-devops": "0.18.0",
    "interactive": "0.4.4"
  }
}

C:\Users\smehan>az version -o jsonc
{
  "azure-cli": "2.9.1",
  "azure-cli-command-modules-nspkg": "2.0.3",
  "azure-cli-core": "2.9.1",
  "azure-cli-nspkg": "3.0.4",
  "azure-cli-telemetry": "1.0.4",
  "extensions": {
    "azure-devops": "0.18.0",
    "interactive": "0.4.4"
  }
}

C:\Users\smehan>az version -o none

C:\Users\smehan>az version -o table
Azure-cli    Azure-cli-command-modules-nspkg    Azure-cli-core    Azure-cli-nspkg    Azure-cli-telemetry
-----------  ---------------------------------  ----------------  -----------------  ---------------------
2.9.1        2.0.3                              2.9.1             3.0.4              1.0.4

C:\Users\smehan>az version -o yaml
azure-cli: 2.9.1
azure-cli-command-modules-nspkg: 2.0.3
azure-cli-core: 2.9.1
azure-cli-nspkg: 3.0.4
azure-cli-telemetry: 1.0.4
extensions:
  azure-devops: 0.18.0
  interactive: 0.4.4

C:\Users\smehan>az version -o yamlc
azure-cli: 2.9.1
azure-cli-command-modules-nspkg: 2.0.3
azure-cli-core: 2.9.1
azure-cli-nspkg: 3.0.4
azure-cli-telemetry: 1.0.4
extensions:
  azure-devops: 0.18.0
  interactive: 0.4.4

C:\Users\smehan>az version -o tsv
2.9.1   2.0.3   2.9.1   3.0.4   1.0.4                                         <-- No headers

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.