Non-breaking at the moment, but the long-term idea is to replace the current widget schema with this.
widget.widget -> widget.componentwidget.dependency_js -> widget.module with "type"='js'
widget.dependency_css -> widget.module with "type"='css'
Modules and components have their own resource functions. These will need to change when bundle releases are figured out. I need to rewrite some UI in another channel, but until then I'm just using stubbed functions for get_module and get_component.
One obscure thing is that all the datum modules exist in the widget bundle. This is because they depend on the widget schema and widgets depend on endpoint. This could be split out into a org.aquameta.core.datum bundle, but datum doesn't really exist without widget. Might as well simplify by merging datum and widget.
Depends on #265.
Non-breaking at the moment, but the long-term idea is to replace the current widget schema with this.
widget.widget->widget.componentwidget.dependency_js->widget.modulewith "type"='js'widget.dependency_css->widget.modulewith "type"='css'Modules and components have their own resource functions. These will need to change when bundle releases are figured out. I need to rewrite some UI in another channel, but until then I'm just using stubbed functions for
get_moduleandget_component.One obscure thing is that all the datum modules exist in the widget bundle. This is because they depend on the widget schema and widgets depend on endpoint. This could be split out into a
org.aquameta.core.datumbundle, but datum doesn't really exist without widget. Might as well simplify by merging datum and widget.