qq
is a interoperable configuration format transcoder with jq
query syntax powered by gojq
. qq
is multi modal, and can be used as a replacement for jq
or be interacted with via a repl with autocomplete and realtime rendering preview for building queries.
Here's some example usage, this emphasizes the interactive mode for demonstrantion, but qq
is designed for usage in shell scripts.
# JSON is default in and output.
cat file.${ext} | qq -i ${ext}
# Extension is parsed, no need for input flag
qq '.' file.xml
# random example: query xml, grep with gron using qq io and output as json
qq file.xml -o gron | grep -vE "sweet.potatoes" | qq -i gron
# get some content from a site with html input
curl motherfuckingwebsite.com | bin/qq -i html '.html.body.ul.li[0]'
# interactive query builder mode on target file
qq . file.json --interactive
From brew:
brew install jfryy/tap/qq
From AUR (ArchLinux):
yay qq-git
From source (requires go
>=1.22.4
)
make install
Download at releases here.
Docker quickstart:
# install the image
docker pull jfryy/qq
# run an example
echo '{"foo":"bar"}' | docker run -i jfryy/qq '.foo = "bazz"' -o tf
qq
is inspired by fq
and jq
. jq
is a powerful and succinct query tool, sometimes I would find myself needing to use another bespoke tool for another format than json, whether its something dedicated with json query built in or a simple converter from one configuration format to json to pipe into jq. qq
aims to be a handly utility on the terminal or in shell scripts that can be used for most interaction with structured formats in the terminal. It can transcode configuration formats interchangeably between one-another with the power of jq
and it has an an interactive repl (with automcomplete)
to boot so you can have an interactive experience when building queries optionally. Many thanks to the authors of the libraries used in this project, especially jq
, gojq
, gron
and fq
for direct usage and/or inspiration for the project.
- support a wide range of configuration formats and transform them interchangeably between eachother.
- quick and comprehensive querying of configuration formats without needing a pipeline of dedicated tools.
- provide an interactive mode for building queries with autocomplete and realtime rendering preview.
qq
is broad, but performant encodings are still a priority, execution is quite fast despite covering a broad range of codecs.qq
performs comparitively with dedicated tools for a given format.
note: these improvements generally only occur on large files and are miniscule otherwise. qq may be slower than dedicated tools for a given format, but it is pretty fast for a broad range of formats.
$ du -h large-file.json
25M large-file.json
# gron large file bench
$ time gron large-file.json --no-sort | rg -v '[1-4]' | gron --ungron --no-sort > /dev/null 2>&1
gron large-file.json --no-sort 2.58s user 0.48s system 153% cpu 1.990 total
rg -v '[1-4]' 0.18s user 0.24s system 21% cpu 1.991 total
gron --ungron --no-sort > /dev/null 2>&1 7.68s user 1.15s system 197% cpu 4.475 total
$ time qq -o gron large-file.json | rg -v '[1-4]' | qq -i gron > /dev/null 2>&1
qq -o gron large-file.json 0.81s user 0.09s system 128% cpu 0.706 total
rg -v '[1-4]' 0.02s user 0.01s system 5% cpu 0.706 total
qq -i gron > /dev/null 2>&1 0.07s user 0.01s system 11% cpu 0.741 total
# yq large file bench
$ time yq large-file.json -M -o yaml > /dev/null 2>&1
yq large-file.json -M -o yaml > /dev/null 2>&1 4.02s user 0.31s system 208% cpu 2.081 total
$ time qq large-file.json -o yaml > /dev/null 2>&1
qq large-file.json -o yaml > /dev/null 2>&1 2.72s user 0.16s system 190% cpu 1.519 total
Note: these unsupported formats are on a roadmap for inclusion.
Format | Input | Output |
---|---|---|
JSON | ✅ Supported | ✅ Supported |
YAML | ✅ Supported | ✅ Supported |
TOML | ✅ Supported | ✅ Supported |
XML | ✅ Supported | ✅ Supported |
INI | ✅ Supported | ✅ Supported |
HCL | ✅ Supported | ✅ Supported |
TF | ✅ Supported | ✅ Supported |
GRON | ✅ Supported | ✅ Supported |
CSV | ✅ Supported | ❌ Not Supported |
Protobuf | ❌ Not Supported | ❌ Not Supported |
HTML | ✅ Supported | ❌ Not Supported |
TXT (newline) | ✅ Supported | ❌ Not Supported |
qq
is not a fulljq
/*q
replacement and comes with idiosyncrasies from the underlyinggojq
library.- the encoders and decoders are not perfect and may not be able to handle all edge cases.
qq
is under active development and more codecs are intended to be supported along with improvements tointeractive mode
.
All contributions are welcome to qq
, especially for upkeep/optimization/addition of new encodings. For ideas on contributions please refer to the todo docs or make an issue/PR for a suggestion if there's something that's wanted or fixes.
This tool would not be possible without the following projects, this project is arguably more of a composition of these projects than a truly original work, with glue code, some dedicated encoders/decoders, and the interactive mode being original work. Nevertheless, I hope this project can be useful to others, and I hope to contribute back to the community with this project.
- gojq:
gojq
is a pure Go implementation of jq. It is used to power the query engine of qq. - fq : fq is a
jq
like tool for querying a wide array of binary formats. - jq:
jq
is a lightweight and flexible command-line JSON processor. - gron: gron transforms JSON into discrete assignments that are easy to grep.
- yq: yq is a lightweight and flexible command-line YAML (and much more) processor.
- goccy: goccy has quite a few encoders and decoders for various formats, and is used in the project for some encodings.
- go-toml: go-toml is a TOML parser for Golang with reflection.