Convert YAML configuration to standard schema #506
Assignees
Comments
|
this relates to #472 |
carlhiggs
changed the title
carlhiggs
added a commit
that referenced
this issue
Mar 18, 2025
…ed schema against the reference standard, and the example configuration against the updated version successfully using jsonschema) towards #506
carlhiggs
added a commit
that referenced
this issue
Mar 18, 2025
…g schema, towards #506; example configuration now validates (although, it is pending improvement and standardisation, eg of dates --- but that will involve breaking changes, so is a separate bigger task
Open
carlhiggs
added a commit
that referenced
this issue
Mar 18, 2025
…ions (i.e. that null is correct value, not 0); towards #506
carlhiggs
added a commit
that referenced
this issue
Mar 18, 2025
…Test workflow appears to pass now, without unintended downstream consequences of modifying pyyaml constructors.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Current configuration approach is complicated for users because of syntax, but also for developers because it is somewhat ad hoc and lacks some consistency/clarity about requirements.
For users the configuration should be abstracted (potentially, there are different options for configuring input); for developers the configuration should standardised with requirements clearly specified (allowing for interchange between formats, including as a GUI for users).
@gboeing and @rschifan recommend JSON Schema.
@ghsci-architecture-and-ux-working-group discussed that @carlhiggs will make a draft in coming weeks and we will discuss at our next software group meeting.
The text was updated successfully, but these errors were encountered: