Hi Everyone!
Do we have a JSON schema that we can use in the Orthanc config file?
Regards,
Yash
Hi Everyone!
Do we have a JSON schema that we can use in the Orthanc config file?
Regards,
Yash
no, sorry.
Best regards,
Alain
Hi Sonaliayash,
A schema for the configuration file would be difficult to create, because plugin-specific (and thus, unknown) data can be stored in the configuration file.
It seems to me that a proper schema would require plugin authors to submit a subschema for their own changes to the configuration file, which would be a quite complex endeavor.
Hey Benjamin,
The subschema part makes sense, but don’t you think having such a feature would be great DX?
Thanks
Don’t get me wrong: I agree that it would be nice!
However, in addition to the actual coding/testing work involved (while there are plenty of more important features in the roadmap/wishlist), doing so would invalidate the existing plugins, which is a bold thing to do! And checking only the “non-plugin” part of the configuration is pretty flaky (what if some plugin actually uses the seemingly invalid field that you’ve just added?)
Maybe there’s an obvious solution that I do not think of.