jq is awesome. However, selecting data out of larger JSON payloads can lead to some hairy jq statements.
This is where Jev comes in.
I built jevq, a small sidecar to jq. Basically, jq handles the structure, and Jev answers a semantic question about each value. Once the values I care about are found, I keep processing with jq like normal.
jq -c '.[]' tickets.json |
jevq "this is an open refund request" |
jq '{id, subject}'
Instead of writing a hacky regex or string match for every way a customer might ask for their money back, I just ask the question.
jq is awesome. However, selecting data out of larger JSON payloads can lead to some hairy jq statements.
This is where Jev comes in.
I built jevq, a small sidecar to jq. Basically, jq handles the structure, and Jev answers a semantic question about each value. Once the values I care about are found, I keep processing with jq like normal.
jq -c '.[]' tickets.json | jevq "this is an open refund request" | jq '{id, subject}'
Instead of writing a hacky regex or string match for every way a customer might ask for their money back, I just ask the question.