json_to_paths
babashka
Our great sponsors
| json_to_paths | babashka | |
|---|---|---|
| 2 | 2 | |
| 66 | 1,711 | |
| - | - | |
| 0.0 | 9.7 | |
| about 3 years ago | about 3 years ago | |
| JSONiq | Clojure | |
| - | Eclipse Public License 1.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.
json_to_paths
-
Interactive Examples for Learning Jq
as a list of jq arguments.
You can use it to make queries or keep track of a documents structure.
https://github.com/TomConlin/json_to_paths
-
A Practical Introduction to jq (and more)
b) may care when the structure (but not the values) change.
so a jq utility[] that spits out all the jq paths for a json files helps in both cases.
[] https://github.com/TomConlin/json_to_paths
babashka
-
Show HN: Bbb – an easy way to build and compile Clojure CLIs with GraalVM
I've been learning Clojure recently and loving it, but one thing I've found myself missing from my Golang days is how easy it is to build and deploy CLI tools in Golang.
With GraalVM it's finally possible to compile Clojure apps into static binaries that give your users a deploy and startup experience similar to Go's, but I found GraalVM very difficult to configure and use, and was often frustrated because not all JVM code is compatible with GraalVM. Worse still, because native-images take a while to build you often don't find out that your working JVM Clojure code won't work as a native-image until it's too late.
BabashkaBins/bbb is my attempt to fix this: it lets you easily run the same codebase under babashka or JVM Clojure, and will automate compiling your project to a static binary for you using GraalVM's native-image. It also takes care of collecting some tweaks that make it easy to use the cli-magic [2] library under babashka, which means you can easily make complex CLI tools with nested subcommands a la git or docker, with all the bells and whistles.
Since babashka is itself compiled under GraalVM, this arrangement provides a other few nice benefits: 1) babashka starts quickly, so you can test your CLI from an actual command line without waiting for the JVM to spin up each time. 2) babashka's codebase contains a treasure trove of GraalVM related tweaks and fixes that using bbb lets you take advantage of in your own CLIs for free, and 3) it functions as a quick sanity check since babashka itself is compiled under GraalVM. If you find yourself doing something that's not GraalVM compatible at least you'll know early!
[1]: https://github.com/borkdude/babashka
-
A Practical Introduction to jq (and more)
```
[1]: https://github.com/borkdude/babashka
What are some alternatives?
jello - CLI tool to filter JSON and JSON Lines data with Python syntax. (Similar to jq)
PowerShell - PowerShell for every system!
cheshire - Clojure JSON and JSON SMILE (binary json format) encoding/decoding
grop - helper script for the `gron | grep | gron -u` workflow
jc - CLI tool and python library that converts the output of popular command-line tools, file-types, and common strings to JSON, YAML, or Dictionaries. This allows piping of output to tools like jq and simplifying automation scripts.
specter-cli - A native Specter CLI, compiled with GraalVM native-image and executed by SCI.
clojure-lsp - Clojure & ClojureScript Language Server (LSP) implementation
jq-web - jq in the browser with emscripten.
tools-deps-native - Run tools.deps as a native binary
jq.py - Python bindings for jq