13 implements download functionality. The download includes the config, but also things specific to the web app, such as experiment name, description, and output.
Should we include all of these? Should experiment name and description become part of the config? Does it make sense to include a version/PID of the classconfig jsonschema, like e.g. vega does?
I guess my main concern is that one should be able reuse the downloaded configuration also outside the web app, e.g. when running class in nodejs.
13 implements download functionality. The download includes the config, but also things specific to the web app, such as experiment name, description, and output.
Should we include all of these? Should experiment name and description become part of the config? Does it make sense to include a version/PID of the classconfig jsonschema, like e.g. vega does?
I guess my main concern is that one should be able reuse the downloaded configuration also outside the web app, e.g. when running class in nodejs.
_Originally posted by @Peter9192 in https://github.com/classmodel/class-web/pull/13#discussion_r1710959913_