feedback VS gron

Just learnt about this GitHub feature although it looks like it has been removed.

Azure skills navigator - the new developer's "Guide to the Cloud"Markdown: An option to highlight a "Note" and "Warning" using blockquote (Beta)

Link to the alternative proposal is in this comment: https://github.com/github/feedback/discussions/16925#discuss...

(I work at GitHub.) We've started using our Discussions product for feedback. You can post a discussion here:

https://github.com/github/feedback/discussions/categories/ge...

> - Why can’t I choose the colors of web sites and applications?

For what it's worth, Firefox lets you edit them:

http://kb.mozillazine.org/index.php?title=UserContent.css&pr...

Not terribly easily, but you can do it for any site. For example I fixed a GitHub bug for myself: https://github.com/github/feedback/discussions/8098#discussi...

I’m really excited for Git’s recent addition of commit signing with SSH keys. It already works with 1Password SSH and I can’t wait for GitHub and Gitlab to support verification!

gron (https://github.com/tomnomnom/gron) to transform it and query and then invert the transformation?

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

> 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

And jless [1] and gron [2].

This is the first I'm hearing of gron, but adding here for completeness sake. Meanwhile, JSON seems to be becoming a standard for CLI tools. Ideal scenario would be if every CLI tool has a --json flag or something similar, so that jc is not needed anymore.

[1] https://jless.io/

[2] https://github.com/tomnomnom/gron