Composable Content Groups

[dbaines]

What problem does this solve?

Creating more than one composable content section on a single record / view.
Say you want a composable content in a sidebar and another in the main area of the page.
This isn't currently possible without hacks or abusing the sectioning component

Current state

For reference, currently the composable config in the model looks like this:

composable: [
  :component_1,
  :component_2,
  :component_3,
]

And the output of the composable content JSON is similar:

components: [{
  component_type: "component_1",
  data: [{
    field1: value,
    field2: value,
  }]
}]

Introducing groups

This change proposes a change to both the crud config and the output:

composable: {
  main: [
    :component_1,
    :component_2,
    :component_3,
  ],
  sidebar: [
    :component_2,
    :component_4,
    :component_5,
  ]
}

components: [{
  main: [{
    component_type: "component_1",
    data: [{
      field1: value,
      field2: value,
    }]
  }],
  sidebar: [{
    component_type: "component_5",
    data: [{
      field1: value,
    }]
  }]
}]

This change in structure will unfortunately mean it's a breaking change.

The code will assume all composable content will always have groups, so even if you aren't utilising groups, make sure you define a default group, eg. "main" or "default"
This will make the UI and implementation consistent and won't rely on hacks checking on whether groups exist or not

Once more than one group is detected, the UI of the composable content screen will update to show tabs to switch between content groups.
If you are only utilising a single group the UI will not change at all.

In your views you can now use composable_json(:main) and composable_data(:sidebar) to access your groups.
These flags also flow through to the existing composable_sections(:main) and composable_sections_with_drafts(:main)

[dbaines]

A lot the code now reads helpers.group or this.state.group which is the current visible group. This means that there is no way to modify anything in a non-visible group. I can't think of any use-cases where a non-visible group would need to be updated (reorder, add item, remove item etc.) but something worth keeping in mind I guess.

[dbaines]

Renamed composableTypes to config to better describe what it is