rb
jp
Our great sponsors
rb | jp | |
---|---|---|
3 | 6 | |
1,488 | 716 | |
- | 1.8% | |
0.0 | 1.1 | |
about 1 year ago | 11 months ago | |
Ruby | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rb
-
Zq: An Easier (and Faster) Alternative to Jq
I like using `jq` to create line-delimited JSON and then using a language I know well (Node) to process it after that point. I find `jq '.[] | select(.location=="Stockholm")'` less readable than something like `nq --filter '({location}) => location === "Stockholm"'` because I'm much more used to Node syntax.
- https://github.com/thisredone/rb is a widely used ruby version of this idea
- https://github.com/KelWill/nq#readme is something similar that I wrote for my own use
- rb: Turns Ruby into a versatile command line utility
-
My latest tutorial, on using Ruby from the command line.
You might be interested by this little script https://github.com/thisredone/rb
jp
-
Jq Internals: Backtracking
I have a hard time suggesting such a thing, because I find JMESPath incredibly inferior to jq's expressiveness, but if you're in the AWS ecosystem much, you may enjoy https://github.com/jmespath/jp#readme which uses the same query language as does awscli (https://docs.aws.amazon.com/cli/latest/userguide/cli-usage-f...). That may at least pay more dividends than keeping jq's language in your head where it will only ever be used by jq
-
using JQ to parse output
Have you tried this utility instead: https://github.com/jmespath/jp
- Zq: An Easier (and Faster) Alternative to Jq
- What tools did you discover that made your work so much easier for DevOps & SRE
-
FX: An interactive alternative to jq to process JSON
There’s also jp, which interprets JMESPath: https://github.com/jmespath/jp
This one has the advantage of being natively understood by aws-cli, meaning you can pass a JMESPath to an AWS call and only receive the filtered / transformed result back.
- Tips on Adding JSON Output to Your CLI App
What are some alternatives?
zed - A novel data lake based on super-structured data
jq - Command-line JSON processor
wsjq - Whitespace interpreter and debugger in jq
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
jid - json incremental digger
fx - Terminal JSON viewer & processor
nq - sed "s/jq .key/nq '({key}) => key'/"
jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure
q - q - Run SQL directly on delimited files and multi-file sqlite databases
scout - Reading and writing in JSON, Plist, YAML and XML data made simple when the data format is not known at build time. Swift library and command-line tool.
mcfly - Fly through your shell history. Great Scott!