cson
groq-test-suite
| cson | groq-test-suite | |
|---|---|---|
| 1 | 1 | |
| 1,333 | 10 | |
| -0.1% | - | |
| 5.7 | 4.7 | |
| 4 months ago | about 1 month ago | |
| CoffeeScript | JavaScript | |
| 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.
cson
-
The Norway Problem
I prefer JSON over YAML because I spend more time confused and burned by the problems caused by it.
I understand that people don't like directly use JSON because it's not very friendly: no comments, no multi-line string, etc.
A great alternative IMHO is cson[0]. It's like JSON to JavaScript but for CoffeeScript (though nobody talks about it nowadays). It has indentation-based syntax, comments, and multiline string which usually don't need to escape. The advantage is it's close enough to JSON which is the canonical format that everybody can agree on nowadays. For YAML and TOML there are too many visual part-aways from JSON.
Or just create a JSON variant that enables comments and the backtick multiline string from JavaScript.
[0] https://github.com/bevry/cson
groq-test-suite
-
The Norway Problem
TOML also has a few restrictions, such as not supporting mixed-type arrays like [1, "hello", true], or arrays at the root of the data. JSON can represent any TOML value (as far as I know), but TOML cannot represent any JSON value.
At my company we use YAML a lot for table-driven tests (e.g. [1]), and this not only means lots of nested arrays, but also having to represent pure data (i.e. the expected output of a test), which requires a format that supports encoding arbitrary data structures.
[1] https://github.com/sanity-io/groq-test-suite/
What are some alternatives?
jsonnet - Jsonnet - The data templating language
yamllint - A linter for YAML files.
strictyaml - Type-safe YAML parser and validator.
lua-patterns - Exposing Lua string patterns to Rust
ron - Rusty Object Notation
tao-data-js - TAO data JavaScript module
edn - Extensible Data Notation
cue - CUE has moved to https://github.com/cue-lang/cue
bip39 - BIP-39 tools using Node and implemented in Coffeescript
toml.io - Source Code for toml.io
jadelet - Pure and simple clientside templates