The old names were actually very confusing. The widget gets passed a row, not a relation. This simplifies the concept and also maps well do what these components accept as parameters.
components
The semantics bundle depends on widget, so eventually I will add all the components to this bundle as well.
Depends on #266
Non-breaking at the moment, but the long-term idea is to replace the current semantics schema with this.
join tables
semantics.relation
->semantics.relation_component
semantics.column
->semantics.column_component
semantics.type
->semantics.type_component
These names could be anything, but this schema had to be forked to reference the new
widget.component
table.text identifiers
text-identifier widget ->
semantics.unique_identifier
There are situations where you may want an identifier without a widget. A semantics component can still be used to wrap this functionality.
functions
semantics.relation_widget()
->semantics.row_component()
semantics.column_widget()
->semantics.field_component()
The old names were actually very confusing. The widget gets passed a row, not a relation. This simplifies the concept and also maps well do what these components accept as parameters.
components
The semantics bundle depends on widget, so eventually I will add all the components to this bundle as well.