Show HN: Flatito, grep for YAML and JSON files

This looks cool!<p>It doesn&#x27;t do quite the same thing, but a tool I&#x27;ve had good luck with for quick-n-dirty grepping of JSON is gron:<p><a href="https:&#x2F;&#x2F;github.com&#x2F;tomnomnom&#x2F;gron">https:&#x2F;&#x2F;github.com&#x2F;tomnomnom&#x2F;gron</a><p>(which I&#x27;m sure I learned about from a thread like this on HN...)<p>It sort of &quot;flattens out&quot; your JSON to allow you to do whatever you want to it (grepping, for one thing!). Then you can even turn gron&#x27;s output back into JSON with `ungron`.<p>Maybe someone will find it a useful toolbox addition, much like the Flatito looks to be!

So I see that the name is derived from an esperanto word (apparently meaning &quot;flatter&quot;) but in spanish it would also mean a small burp (&quot;flato&quot; being an informal term for burp). Which I still like as a name ;)

I usually have to use JMESPath queries semi-regularly. Every time I do it feels like I&#x27;m starting over for the first time. I&#x27;d love something that made more sense to me, but in most cases I&#x27;m stuck with what I have due to restrictions on what I can use at work.

This till doesn&#x27;t give any context about the keys context, what&#x27;s the full path of the key? That&#x27;s critically important.

This is the kind of thing Nushell is already really good at.

Is this different from yq?

What I often use to just get the full key paths is yq (<a href="https:&#x2F;&#x2F;github.com&#x2F;mikefarah&#x2F;yq">https:&#x2F;&#x2F;github.com&#x2F;mikefarah&#x2F;yq</a>), piping into grep when necessary<p><pre><code> yq -o=props &lt;file&gt; </code></pre> e.g.<p><pre><code> kind = Ingress metadata.name = hello spec.rules.0.host = localhost spec.rules.0.http.paths.0.pathType = ImplementationSpecific spec.rules.0.http.paths.0.backend.service.name = hello spec.rules.0.http.paths.0.backend.service.port.number = 80 </code></pre> The one drawback I&#x27;ve encountered so far are multi-doc files - yq can certainly handle those, but you have to script the loop yourself.

related project, gron: <a href="https:&#x2F;&#x2F;github.com&#x2F;tomnomnom&#x2F;gron">https:&#x2F;&#x2F;github.com&#x2F;tomnomnom&#x2F;gron</a><p><pre><code> ▶ gron &quot;https:&#x2F;&#x2F;api.github.com&#x2F;repos&#x2F;tomnomnom&#x2F;gron&#x2F;commits?per_page=1&quot; | fgrep &quot;commit.author&quot; json[0].commit.author = {}; json[0].commit.author.date = &quot;2016-07-02T10:51:21Z&quot;; json[0].commit.author.email = &quot;mail@tomnomnom.com&quot;; json[0].commit.author.name = &quot;Tom Hudson&quot;;</code></pre>