JSON Schema version

[yorek]

Summary

Create a new JSON Schema every time for every new release (if there are changes in the schema)

Motivation

Using JSON schema simplifies a lot the creation of the JSON configuration file when using a modern tool like VS Code. It is important that all the features supported by DAB are reflected (and somehow documented) in the JSON schema.

Functional Specifications

DAB engine should be able to parse and understand a JSON configuration file that is using the same version schema of the engine. This helps a developer to migrate a schema to a new version just by changing the JSON schema reference specified int dab-config.json file. For example, the JSON schema used by version 0.2.52 of dab will be named dab.0.2.52.schema.json and the dab-config.json file can use it simply as per the following sample:

{
    "$schema": "../schemas/dab.0.2.52.schema.json",
    "data-source": {
        "database-type": "",
        "connection-string": ""
    },
    "runtime": {
        "host": {
            "mode": "development"
        }
    },
    "entities": {
    }
}