scout
jp
| scout | jp | |
|---|---|---|
| 8 | 6 | |
| 127 | 718 | |
| - | 1.1% | |
| 4.2 | 1.1 | |
| 2 months ago | 11 months ago | |
| Swift | 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.
scout
-
Is there a neat way to work with deeply-nested JSON?
I developed a library that is better suited for such cases than plain Decodable. You can specify a path in the data and at the end of the path specify a Decodable type to be instantiated from the data.
-
A different way of reading JSON: Part 2!
Not 100% sure but you might find Scout interesting for your needs
-
Best practices for parsing dynamic/unstructured JSON?
I developed Scout for this exact purpose because I had to find a solution to get a value when the data structure is not known at build time.
- Scout 2. ;. ;
-
Get XML, parse output, get a date and calculate differences?
If you are ok to use a program, you can use Scout like that: curl [your curl request here] | scout read -f xml "a-valid-date"
-
Guidance in building a .json config file with bash script.
For a clear and simple syntax, you can take a look at Scout.
-
Take that, Codable
I have been working myself on Scout to work on data when the format is not known at build time (for instance with a generic command line tool). And I have never had the tuple decoding requested. Although this might be useful for some people.
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?
python-benedict - :blue_book: dict subclass with keylist/keypath support, built-in I/O operations (base64, csv, html, ini, json, pickle, plist, query-string, toml, xls, xml, yaml), s3 support and many utilities.
jq - Command-line JSON processor
ZippyJSON - A much faster version of JSONDecoder
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
BackedCodable - Powerful property wrapper to back codable properties.
fx - Terminal JSON viewer & processor
jp - Validate and transform JSON with Bash
jet - CLI to transform between JSON, EDN, YAML and Transit using Clojure
EVReflection - Reflection based (Dictionary, CKRecord, NSManagedObject, Realm, JSON and XML) object mapping with extensions for Alamofire and Moya with RxSwift or ReactiveSwift
jid - json incremental digger
simdjson - Parsing gigabytes of JSON per second : used by Facebook/Meta Velox, the Node.js runtime, ClickHouse, WatermelonDB, Apache Doris, Milvus, StarRocks
rq - Record Query - A tool for doing record analysis and transformation