Manuel Gundlach

@lerks in fact described pretty well the reason I decided not to use a boolean flag. Using a boolean flag instead of just duplicating the code wouldn't even eliminate all...

I was going to leave a note about this, but now it definitely seems like this should be of interest: @t-lenz had the same idea some time ago and went...

If CMS would switch to a standard made for configuration files, like TOML, it would indeed make configuration files a lot more readable and ease configuration significantly. See [this snippet](https://gist.github.com/magula/b5bd7a3451bb35595c693b6a12574b71)...

JSON5 would certainly be less intrusive, so it could well be the best option if we want to preserve compatibility! But it is still harder to read and write than...

Yes, not grouping the keys into sections, thus changing way less code is definitely safer, and preserving backwards-compatibility is also a big plus. I am indecisive on this, but I...

> Yeah that sounds reasonable (I assume these aliases would work both in the legacy JSON file and the new TOML one?) Yes, they will work in both. > As...

I removed the section headers (or table headers, as TOML calls it) in the last commit, so the structure is as before. However, there seems to be no (legible) way...