Create JSON schema for config about madness

[EmilyGraceSeville7cf]

Here is a PR to SchemaStore.

[EmilyGraceSeville7cf]

So what will be the course of action when one of these schemas you made needs a new version?

Just create a new JSON schema with some edits incorporating new features. ;) In VS Code in such situation, editor notifies that multiple schemas match some file and lets to chose what file version is used.

[DannyBen]

Welcome collaborator, as usual :)

[DannyBen]

Here is a PR to SchemaStore.

Doesn't SchemaStore have some way of handling versions?

Imagine anytime any of these schemas are updated on the master branch, it will prevent all users of an older version from using it, and in some cases - when the master contains an unreleased code - it will prevent everybody from using it.

[EmilyGraceSeville7cf]

Doesn't SchemaStore have some way of handling versions?

It does. ;) There are two ways to implement multiple version support: via catalog.json from SchemaStore or directly inside schema via oneOf keyword. The second approach is suitable when there is something to identify file version directly. For instance, go-task tool has version key inside file to switch between several syntax versions. In other words, the first aproach (via catalog.json) suits our situation.

When there are multiple versions presented via version key in catalog.json there are also the same amount of corresponding JSON schemas, file per version.

[DannyBen]

So what will be the course of action when one of these schemas you made needs a new version?