I have generated the full JSON schema for the accelerator and I'm now writing the documentation for how to use it to get help to write the documentation.
Here is the current version:
accelerator.schema.json
I plan to include two options:
-
Use the JSON schema functionality in VS Code: I'm working on figuring out all the extensions and settings needed for this.
-
Use the MetaConfigurator: for this it would be useful with more testers to find potential bugs both in the schema and in the metaconfigurator. I have changed the schema now to use oneOf instead of anyOf which seems so far to work and provides a nicer user interface. I have also found some bugs that the developers said they are planning to fix before next week.
For now I think we should use the development version to get the bug fixes: https://metaconfigurator.github.io/meta-configurator/data
Then the question is where to publish the schema. In the metaconfigurator (and maybe also in VS Code, need to check) it's possible to load a schema from an url which is very convenient. But that raises where on github this schema should be stored.
I can think of three options:
- In the pyaml repository
- In a separate pyaml-schema repository
- In the pyaml-test-lattice repository
What do you think? I'm currently leaning towards maybe a separate repository since the schema includes more than just classes that are in the pyaml repository. It's also possible that we can have there schemas for subparts of the accelerator to make it easier to use the external tools also if you want to use the option to separate the configuration into many files.
I have generated the full JSON schema for the accelerator and I'm now writing the documentation for how to use it to get help to write the documentation.
Here is the current version:
accelerator.schema.json
I plan to include two options:
Use the JSON schema functionality in VS Code: I'm working on figuring out all the extensions and settings needed for this.
Use the MetaConfigurator: for this it would be useful with more testers to find potential bugs both in the schema and in the metaconfigurator. I have changed the schema now to use
oneOfinstead ofanyOfwhich seems so far to work and provides a nicer user interface. I have also found some bugs that the developers said they are planning to fix before next week.For now I think we should use the development version to get the bug fixes: https://metaconfigurator.github.io/meta-configurator/data
Then the question is where to publish the schema. In the metaconfigurator (and maybe also in VS Code, need to check) it's possible to load a schema from an url which is very convenient. But that raises where on github this schema should be stored.
I can think of three options:
What do you think? I'm currently leaning towards maybe a separate repository since the schema includes more than just classes that are in the pyaml repository. It's also possible that we can have there schemas for subparts of the accelerator to make it easier to use the external tools also if you want to use the option to separate the configuration into many files.