json5
Our great sponsors
| ansible-dhall-jsonnet | json5 | |
|---|---|---|
| 2 | 94 | |
| 6 | 6,291 | |
| - | 1.3% | |
| 0.0 | 0.0 | |
| over 3 years ago | 5 months ago | |
| Dhall | 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.
ansible-dhall-jsonnet
-
What Is Wrong with TOML?
Maybe you'd like jsonnet: https://jsonnet.org/
I find it particularly useful for configurations that often have repeated boilerplate, like ansible playbooks or deploying a bunch of "similar-but" services to kubernetes (with https://tanka.dev).
Dhall is also quite interesting, with some tradeoffs: https://dhall-lang.org/
A few years ago I did a small comparison by re-implementing one of my simpler ansible playbooks: https://github.com/retzkek/ansible-dhall-jsonnet
-
Intercal, YAML, and Other Horrible Programming Languages
A few months ago I explored using Dhall and Jsonnet to re-write an Ansible playbook [0,1]. I wanted to like Dhall, but found the type system got in the way more than it helped, while Jsonnet was very productive and a huge improvement over YAML.
[0] https://www.kmr.me/posts/dhall_jsonnet
[1] https://github.com/retzkek/ansible-dhall-jsonnet
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?
Pulumi - Pulumi - Infrastructure as Code in any programming language. Build infrastructure intuitively on any cloud using familiar languages 🚀
Json.NET - Json.NET is a popular high-performance JSON framework for .NET
wasp - The fastest way to develop full-stack web apps with React & Node.js.
hjson-js - Hjson for JavaScript
config - configuration library for JVM languages using HOCON files
jq - Command-line JSON processor [Moved to: https://github.com/jqlang/jq]
dhall-lang - Maintainable configuration files
toml - Tom's Obvious, Minimal Language
ShellCheck - ShellCheck, a static analysis tool for shell scripts
jsonnet - Jsonnet - The data templating language
RailsConfig - Easiest way to add multi-environment yaml settings to Rails, Sinatra, Padrino and other Ruby projects.
sublime-hjson - Hjson support for Sublime Text