3 ms·

Nice! This is the kind of obvious tool that once it exists, you can’t really grok the fact it did not earlier, and that it took until now to exist.

dmos62 5y ago
> grok A good opportunity to introduce `gron` to those unfamiliar! ▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page=1" | fgrep "commit.author" json[0].commit.author = {}; json[0].commit.author.date = "2016-07-02T10:51:21Z"; json[0].commit.author.email = "mail@tomnomnom.com"; json[0].commit.author.name = "Tom Hudson"; https://github.com/tomnomnom/gron https://github.com/tomnomnom/gron
- rsync 5y ago
  "A good opportunity to introduce `gron` to those unfamiliar!" Thank you - appreciated. I haven't done much work with json but have had reasons recently to do so - and I immediately saw how difficult it was to pipeline to grep ... But what I still don't understand is that some json outputs I see have multiple values with the exact same name (!) and that still seems "un-grep-able" to me ... What am I missing ?
  - croon 5y ago
    The json output likely contains multiple objects. Can you request more specifically the object(s) you need and grep on that?
  - dmos62 5y ago
    You might be missing a change in index: `obj[0].prop` vs `obj[1].prop`. Or, your JSON might have the same property defined multiple times: `{a:1, a:2}` (though I'm not sure how gron handles that situation).
    - lvncelot 5y ago
      > (though I'm not sure how gron handles that situation). It seems both gron and jq only use the value that has been defined last: ~ echo '{"a":1,"a":2}' | gron json = {}; json.a = 2; ~ echo '{"a":1,"a":2}' | jq { "a": 2 }
  - dotancohen 5y ago
    > But what I still don't understand is that some json > outputs I see have multiple values with the exact same name This is neither explicitly allowed nor explicitly forbidden by the JSON spec. It is implementation dependent upon how to handle - does one value override the other? Should they be treated as an array? In practice, this situation is usually carefully avoided by services that produce JSON. If you are interfacing with a service that does produce duplicate values, I'd be interested in seeing it for curiosity's sake. If you are writing a service and this is the output, then I implore you to reconsider!
matsemann 5y ago
There are already tools for xpath, but using css selectors is much more aligned with what I write every day, so that's nice.
- harperlee 5y ago
  Yes, and awk and others. I meant something semantically closer to the need, with css selectors.
ptwt 5y ago
It did write it a few years ago. https://github.com/plainas/tq https://github.com/plainas/tq
- mcnesium 5y ago
  and I use it almost every day. It's great, thank you very much!
natrys 5y ago
It's not novel obviously. I have been using pup[1] for years. And xidel[2] is probably older. [1] https://github.com/ericchiang/pup https://github.com/ericchiang/pup [2] https://github.com/benibela/xidel https://github.com/benibela/xidel
mcovey 5y ago
I have been using hxselect from the html-xml-utils package to do this for many, many years. It doesn't handle malformed HTML that well but can be coaxed into working about 90% of the time, with the help of the other included package hxclean or something like html-tidy.

dmos62 5y ago

> grok A good opportunity to introduce `gron` to those unfamiliar! ▶ gron "https://api.github.com/repos/tomnomnom/gron/commits?per_page=1" | fgrep "commit.author" json[0].commit.author = {}; json[0].commit.author.date = "2016-07-02T10:51:21Z"; json[0].commit.author.email = "mail@tomnomnom.com"; json[0].commit.author.name = "Tom Hudson"; https://github.com/tomnomnom/gron https://github.com/tomnomnom/gron

rsync 5y ago
"A good opportunity to introduce `gron` to those unfamiliar!" Thank you - appreciated. I haven't done much work with json but have had reasons recently to do so - and I immediately saw how difficult it was to pipeline to grep ... But what I still don't understand is that some json outputs I see have multiple values with the exact same name (!) and that still seems "un-grep-able" to me ... What am I missing ?
- croon 5y ago
  The json output likely contains multiple objects. Can you request more specifically the object(s) you need and grep on that?
- dmos62 5y ago
  You might be missing a change in index: `obj[0].prop` vs `obj[1].prop`. Or, your JSON might have the same property defined multiple times: `{a:1, a:2}` (though I'm not sure how gron handles that situation).
  - lvncelot 5y ago
    > (though I'm not sure how gron handles that situation). It seems both gron and jq only use the value that has been defined last: ~ echo '{"a":1,"a":2}' | gron json = {}; json.a = 2; ~ echo '{"a":1,"a":2}' | jq { "a": 2 }
- dotancohen 5y ago
  > But what I still don't understand is that some json > outputs I see have multiple values with the exact same name This is neither explicitly allowed nor explicitly forbidden by the JSON spec. It is implementation dependent upon how to handle - does one value override the other? Should they be treated as an array? In practice, this situation is usually carefully avoided by services that produce JSON. If you are interfacing with a service that does produce duplicate values, I'd be interested in seeing it for curiosity's sake. If you are writing a service and this is the output, then I implore you to reconsider!

matsemann 5y ago

There are already tools for xpath, but using css selectors is much more aligned with what I write every day, so that's nice.

harperlee 5y ago
Yes, and awk and others. I meant something semantically closer to the need, with css selectors.

ptwt 5y ago

It did write it a few years ago. https://github.com/plainas/tq https://github.com/plainas/tq

mcnesium 5y ago
and I use it almost every day. It's great, thank you very much!

natrys 5y ago

It's not novel obviously. I have been using pup[1] for years. And xidel[2] is probably older. [1] https://github.com/ericchiang/pup https://github.com/ericchiang/pup [2] https://github.com/benibela/xidel https://github.com/benibela/xidel

mcovey 5y ago

I have been using hxselect from the html-xml-utils package to do this for many, many years. It doesn't handle malformed HTML that well but can be coaxed into working about 90% of the time, with the help of the other included package hxclean or something like html-tidy.