You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when a flow's configuration is resolved... it could be written as .config/sr3/comp/config/configuration.json
and we could have a json schema file written to .config/sr3/configuration_schema.json
with the two could have a structured editing of configs using a WYSIWIG editor...
anyways... the schema can constrain the values, e.g. for set types to have choices.
Of course... this is kind of one way... once you start editing in json, you can't get back to the input config format.
dunno... might be a fun student project.
The text was updated successfully, but these errors were encountered:
This becomes more helpful because the current syntax does not express scope at all, and in upcoming changes... aka multibroker/multi-queue support, the scope of many settings changes. (#35 ... some more...)
when a flow's configuration is resolved... it could be written as .config/sr3/comp/config/configuration.json
and we could have a json schema file written to .config/sr3/configuration_schema.json
with the two could have a structured editing of configs using a WYSIWIG editor...
anyways... the schema can constrain the values, e.g. for set types to have choices.
Of course... this is kind of one way... once you start editing in json, you can't get back to the input config format.
dunno... might be a fun student project.
The text was updated successfully, but these errors were encountered: