hujson
json5
| hujson | json5 | |
|---|---|---|
| 10 | 94 | |
| 564 | 6,301 | |
| 0.9% | 0.9% | |
| 0.0 | 0.0 | |
| 6 months ago | 5 months ago | |
| Go | JavaScript | |
| BSD 3-clause "New" or "Revised" License | GNU General Public License v3.0 or later |
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.
hujson
- JSON for Humans (JWCC: JSON with comments and trailing commas)
-
Ron: Rusty Object Notation
That, and comments!
Personally, I really hope Human JSON, https://github.com/tailscale/hujson , will take over!
-
Unmarshal text with Go reflection - usage and internals of a library for line-oriented text
I also like the approach that the hujson library takes, where everything is a type Literal []byte and you can call (Literal).Bool(), (Literal).String(), (Literal).Int() or (Literal).Float() on it and it gives you the corresponding value out of it (or the zero value). So kinda like dynamic variables that can store anything.
-
Internet Object – A JSON alternative data serialization format
One of the variants that permit comments: https://github.com/tailscale/hujson
- HuJSON - JSON for Humans (comments and trailing commas)
- Tailscale/hujson: HuJSON: JSON for Humans (comments and trailing commas)
json5
- JSON5 – JSON for Humans
- Why the fuck are we templating YAML? (2019)
-
I pre-released my project "json-responder" written in Rust
JSON5 support
-
topoconfig: enhancing config declarations with graphs
Meanwhile, formats have been evolving (JSON5, YAML), config entry points are constantly changing. These fluctuations, fortunately, were covered by tools like the cosmiconfig.
-
That's a Lot of YAML
I think JSON5 is fairly close to this: https://json5.org
I reckon the only thing it's missing to be truly accessible to non-techies is that string values still need to be quoted, i.e. you can't have:
key: this is my value
(I'm definitely not saying it would be a good idea to allow quotes to be dropped, just that that's the only potential stumbling block I see for non-techies.)
-
XML is better than YAML
I believe that's JSON5.
https://github.com/json5/json5
It's my preferred configuration file format, it fixes all the problems I have with JSON (trailing commas, comments) without turning it into a mess full of gotchas like YAML.
- Fx – Terminal JSON Viewer
- What Is Wrong with TOML?
-
🚀 'GET' API in API Maker
JSON 5 support
-
TySON: a native go library that lets you use TypeScript as an embedded configuration language without depending on Node or V8
I would like to see mention of JSON5 which is 11 years its elder. For comments in JSON, JSON5 is a good starting point.
What are some alternatives?
zed - A novel data lake based on super-structured data
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
jsonschema-key-compression - Compress json-data based on its json-schema while still having valid json
hjson-js - Hjson for JavaScript
set - Package set is a small wrapper around the official reflect package that facilitates loose type conversion and assignment into native Go types.
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
Dixy - Data format based on dictionaries
toml - Tom's Obvious, Minimal Language
simdjson - Parsing gigabytes of JSON per second : used by Facebook/Meta Velox, the Node.js runtime, ClickHouse, WatermelonDB, Apache Doris, Milvus, StarRocks
jsonnet - Jsonnet - The data templating language
proposal-json-superset - Proposal to make all JSON text valid ECMA-262
sublime-hjson - Hjson support for Sublime Text