Overthink JSON #3

New Issue

Dennis · 2019-01-13T10:24:19Z

Dennis commented

2019-01-13 10:24:19 +00:00

Right now, JSON is used to save all configuration, but also all messages. It is probably not the most suitable format.

Think about other formats, for example, YAML.

Right now, JSON is used to save all configuration, but also all messages. It is probably not the most suitable format. Think about other formats, for example, [YAML](https://wiki.python.org/moin/YAML).

Dennis self-assigned this 2019-01-13 10:24:19 +00:00

Dennis added the

enhancement

label 2019-01-13 10:24:19 +00:00

Dennis commented

2019-01-13 17:19:41 +00:00

Alternatives to JSON:

All these languages support comments and multi line strings (which are the main reasons to move away from traditional JSON).

I probably prefer Hjson because it has a similar structure to JSON and because it is backwards compatible with JSON.

Alternatives to JSON: * [YAML](https://wiki.python.org/moin/YAML) * [TOML](https://github.com/toml-lang/toml) * [Hjson](https://hjson.org/) All these languages support comments and multi line strings (which are the main reasons to move away from traditional JSON). I probably prefer Hjson because it has a similar structure to JSON and because it is backwards compatible with JSON.

Dennis referenced this issue from a commit

2019-01-14 22:49:44 +00:00

Transitioned from JSON to Hjson. Closes #3 All configuration files and all messages files should now preferrable be done in Hjson. This format supports, i.a. features, multi line strings and commenting. This greatly improves readability. All installation and documentation files are also updated in this commit.

Dennis closed this issue

2019-01-14 22:49:44 +00:00

Sign in to join this conversation.