hjson-js VS strictyaml

By the way.. if you use the hjson parser you can add comments to json files :) https://hjson.github.io/

I wish this took off https://hjson.github.io. I like it much more than yaml.

I don't know anything about VueJS either but HJSON is pretty cool in that regard https://hjson.github.io/

> Another difficult problem was checking for correct indentation visually (because the configuration is YAML-based and indentation matters).

why yaml? I hate it so much! my eyes hurt looking at it?

why not using https://hjson.github.io/ ?

HJSON [0] is also another format that tries to make it easier for humans to read / write json.

[0] https://hjson.github.io/

well there are json alternatives which fit this bill, such as HJSON.

https://hjson.github.io/

might not be as "common" but it has good implementations for many languages.

zdpack also pre-processes datapacks, allowing json files to be written in hjson or yaml, in addition to allowing a special extensible super-set of MCFunction I call CommandScript. You can check the github page for a quick overview of CommandScript.

NestedText already is the way I use YAML; everything is intepreted as a string. I have some trust in my YAML parser to not mangle most strings. I could use NestedText, but users would be unfamiliar with it, and IIRC the only parsers are in Python. But then I could use StrictYaml too https://github.com/crdoconnor/strictyaml

you can stick to a subset of YAML syntax (e.g. strictYAML)

YAML stands for "YAML Ain’t Markup Language" - this is known as a recursive acronym. YAML is often used for writing configuration files. It’s human readable, easy to understand and can be used with other programming languages. Although YAML is commonly used in many disciplines, it has received criticism on the amoutn of whitespace .yml files have, difficulty in editing, and complexity of the standard. Despite the criticism, properly using YAML ensures that you can reproduce the results of a project and makes sure that the virtual environment packages play nicely with system packages. (If you're looking for another way to share environments there are other alternatives to YAML which include StrictYAML (a type-safe YAML parser) and NestedText)

The example you linked provides this as an example of a YAML document that he wants his format to support.

That safe subset exists and is implemented in a number of languages. It is called strict-yaml: https://hitchdev.com/strictyaml/

StrictYAML\ (33 comments)

To me those are in the category of "nice to have", and the problem is that every developer has different preferences for these [1] [2]. But the main features of StrictYaml, like supporting comments and less syntactic noise, I think are pretty uncontroversial, and perhaps it's worth it to get people to switch over for those alone. It doesn't need to be perfect, it just needs to be a significant enough improvement over JSON, and I'd say those two features are more than enough

[1]: https://github.com/crdoconnor/strictyaml/issues/37

[2]: https://github.com/crdoconnor/strictyaml/issues/38