jp
rq
Our great sponsors
| jp | rq | |
|---|---|---|
| 6 | 10 | |
| 716 | 2,255 | |
| 1.8% | - | |
| 1.1 | 3.2 | |
| 11 months ago | 4 months ago | |
| Python | Rust | |
| Apache License 2.0 | 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.
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
rq
- Jc – JSONifies the output of many CLI tools
-
Shell Script Best Practices, from a decade of scripting things
Not sure what it is doing more...I'm referring to this rq: https://github.com/dflemstr/rq#format-support-status
It converts to/from the listed formats.
There is also `jc` (written in Python) with the added benefit that it converts output of many common unix utilities to json. So you would not need to parse `ip` for example.
https://github.com/kellyjonbrazil/jc
-
What debugging/monitoring method do you use? Lately, I have been using the Saleae Logic Analyzer to monitor the signals exchanged among the boards of my embedded network. I find it really cool, but do you have any other recommendations? What do you use?
In robotics most relevant signals are seen by the software. My current pattern is to log everything to MessagePack files (e.g. using mpacklog in Python or palimpsest in C++), then dump and plot the data later on using handy command-line tools like jq and rq.
- Tombl – Easily query .toml files from bash
- rq: Universal convertor between structured data (JSON, MessagePack, CBOR, etc.)
- Show HN: utt, the Universal Text Transformer
- FX: An interactive alternative to jq to process JSON
- Tips on Adding JSON Output to Your CLI App
-
Miller CLI – Like Awk, sed, cut, join, and sort for CSV, TSV and JSON
There's also rq (record query)[1] that also supports CSV and JSON but not TSV though. It's written in Rust.
[1] https://github.com/dflemstr/rq
-
What's everyone working on this week (27/2021)?
Ish. https://github.com/dflemstr/rq/ It removed its processing language a while ago. It's still a very useful tool, though. Imho, it's a bigger pity that it can't highlight YAML on output, or parse YAML 1.1.
What are some alternatives?
jq - Command-line JSON processor
fx - Terminal JSON viewer & processor
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
if-decompiler - Decompile Glulx storyfiles into C code
jiq - jid on jq - interactive JSON query tool using jq expressions
jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure
hello-actix - Hello, actix!
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.
jid - json incremental digger
dprint - Pluggable and configurable code formatting platform written in Rust.