Is there a JSON schema available for the JSON configuration files?

[svdoever]

It is quite a hassle to get configuration files right. Some documentation samples use "True", others use true, properties are documented, but it is not clear if they are still supported...

[MrHinsh]

No, there is no Schema.

They should be consistent as they should all be booleans. Booleans are all serialised and de-seralised the same.

Do you have an example of an inconsistency in handling booleans that I can trace?

Samples in the text may become out of data, but we have a Samples section with defaults and samples that are all generated from code. They are always accurate.

I'm also fairly sure that true and "true" are treated the same on injestion.

[bldcm]

I think svdoever's observation is valid, getting configuration files right is quite the hassle. Documentation examples don't always work, init gives different formats than what is documented, not all the options are documented for various object types.

Don't have a specific example right now, just echoing svdoever's frustration that understanding the format of the config file and what it should look like and what the available options are is not trivial.

[MrHinsh]

All the code in the "Samples" section in the documentation is generated as is the list of "parameters". They are almost always up to date. (I say almost as it requires a manual run of the docgenerator)

Any sample in the text is illustrative, and represent a point in time when they were written.

Init samples match the "samples" and "parameters" and the output of "upgrade".

You can always push your config through "upgrade" to cleanse it of anything that's not correct.

As all the configs are generated from the code, I'm not sure how to also generate a schema at runtime. Especially as there is no central config definition! It's extendable and dynamic. There are few places in the code where all the objects are known and accessable.

I think there is an "init" option with everything which reflects all the valid object types...

Id happily Review and collaborate on a PR to have a schema if it is possible.