cargo info doesn't allow to specify output-format

[0x8f701]

Problem

it'll be good to support output-format

Proposed Solution

No response

Notes

No response

[epage]

What other output format would you want and what is the use care for it?

[0x8f701]

@epage output format allow us to integrate other tools. I always want to be productive so I have the following alias:

# instead of seaching the crate and click to go to the repository, I use cbrowse
function cbrowse
  if test -n "$argv[1]"
    open -u (cargo info $argv[1] | grep repository | awk '{print $2}')
  end
end

# instead of seaching the crate and find it's repository url, I use cclone
function cclone
  if test -n "$argv[1]"
    git clone (cargo info $argv[1] | grep repository | awk '{print $2}')
  end
end

in the future I may come up with other scripts for handling things like features, if it's displayed as json then things may be easier

[epage]

Is there reason you want to use this over cargo metatdata? That is generally our answer for programmatic use. This is a UX focused command that we can change the output on as needed.

[0x8f701]

@epage cargo metadata is for local crates, cargo info is for crates on crates.io, in my case it's for for things on crates.io because it contains many more than local ones

[epage]

Would your needs be covered by #11034?