In #28 I suggest to create a generic ConfigEditor component to use in the different data sources. After a first revision, I don't think that's the best path forward, it forces to create some strict structure of the configuration that may be difficult to update and understand.
Rather than exposing a ConfigEditor, I have created two wrapper components around the ResourceSelector and the Input components to adapt them to the ConfigEditor requirements.
Ref: #28
In #28 I suggest to create a generic
ConfigEditor
component to use in the different data sources. After a first revision, I don't think that's the best path forward, it forces to create some strict structure of the configuration that may be difficult to update and understand.Rather than exposing a
ConfigEditor
, I have created two wrapper components around theResourceSelector
and theInput
components to adapt them to theConfigEditor
requirements.