JSON output for the various commands

[rgrinberg]

I think only the gist subcommand supports this but it would be nice if all the commands did.

[dsheets]

Do you want raw JSON from the wire or would a reserialization suffice?

[rgrinberg]

Reserialization should be fine. As long as the differences don't affect
semantics. E.g. formatting or key order

On Mon, Sep 19, 2016, 12:41 PM David Sheets [email protected]
wrote:

Do you want raw JSON from the wire or would a reserialization suffice?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
#102 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIe-6j2P1d-HDb9vTgyDzLd37WKC9zDks5qrrsegaJpZM4H6OsM
.

[dsheets]

Ah, I think it won't work then because we only guarantee to parse a subset of the API so unknown fields, etc would be dropped. What is your use case?

[rgrinberg]

My main use case is ad hoc scripts coupled with jq. I could see this perhaps
being useful when debugging.

On 09/19, David Sheets wrote:

Ah, I think it won't work then because we only guarantee to parse a subset of the API so unknown fields, etc would be dropped. What is your use case?

You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub:
#102 (comment)