gron VS fx

This looks cool!

It doesn't do quite the same thing, but a tool I've had good luck with for quick-n-dirty grepping of JSON is gron:

https://github.com/tomnomnom/gron

(which I'm sure I learned about from a thread like this on HN...)

It sort of "flattens out" your JSON to allow you to do whatever you want to it (grepping, for one thing!). Then you can even turn gron's output back into JSON with `ungron`.

Maybe someone will find it a useful toolbox addition, much like the Flatito looks to be!

It buffers all of its output statements in memory before writing to stdout:

https://github.com/tomnomnom/gron/blob/master/main.go#L204

Have you tried `gron`?

It converts your nested json into a line by line format which plays better with tools like `grep`

From the project's README:

▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page..." | fgrep "commit.author"

json[0].commit.author = {};

json[0].commit.author.date = "2016-07-02T10:51:21Z";

json[0].commit.author.email = "[email protected]";

json[0].commit.author.name = "Tom Hudson";

https://github.com/tomnomnom/gron

It was suggested to me in HN comments on an article I wrote about `jq`, and I have found myself using it a lot in my day to day workflow

Obligatory reference to "gron" ("make JSON greppable"), which I find to be quite useful for many common use cases:

https://github.com/tomnomnom/gron

> So all I want is a tool to go from json => line oriented and I will do the rest with the vast library of experience I already have at transformations on the command line.*

The tool for that is likely https://github.com/tomnomnom/gron

If JQ is too much, see GRON &| Miller

gron transforms JSON into discrete assignments to make it easier to grep for what you want https://github.com/tomnomnom/gron

Miller is like awk, sed, cut, join, and sort for data formats such as CSV, TSV, JSON, JSON https://github.com/johnkerl/miller

There's also this awesome tool to make JSON interactively navigable in the terminal:

https://fx.wtf

Using awk/sed to parse json seems to be using the wrong tool for the job.

As an alternative to jq with easier to remember syntax, see https://fx.wtf/

Recent discussion: https://news.ycombinator.com/item?id=37567009

Neat! You mentioned not getting the hang of jq, have you played with fx?

This looks like something I'd use often. Thanks for creating it! For anyone who's not familiar, Anton is also behind the highly useful fx[0] for wrangling JSON data in the terminal.

[0] https://github.com/antonmedv/fx