Aggregate Fieldtype

[aerni]

I'm building a fieldtype that acts as a wrapper for multiple fields. One of the reasons is to save the data in a separate array.

I want this:

seo:
  title: 'A title'
  description: 'Description'

… not this:

title: 'A title'
description: 'Description'

My fieldtype looks the same as the SeoProFieldtype and ResponsiveFieldtype.

The problem with this approach is that the syncable property on the publish-field component doesn't work as expected. It just works for the wrapper fieldtype itself but not for the fields within. I could imagine that there are other issues with this approach as well.

My proposal is a new aggregate fieldtype that can wrap multiple fields. This might be connected to the UI Fieldtype idea.

[aerni]

I just realized that this could probably also be done with fieldsets. Fieldsets already serve as a wrapper for multiple fields. You could add an option to save the data of the imported fieldset in its own key. Similar to the prefix option.

The only drawback with this approach is that you lose the capabilities of a true fieldtype with its PHP file.

[aerni]

I dug a little deeper. If you wanted the sync feature to work on each field, we'd need to make sure, that each field is pushed to the localizedFields array in the store. Probably also need to change some other things.

https://github.com/statamic/cms/blob/6d1ebe950ca397e98b0a20ef4c9a6dfd6b21ec25/resources/js/components/publish/Field.vue#L182-L184

The same "only top-level fields can be localized" issue goes for Bard, Replicator, and Grid fieldtype. Might be connected to this: #439

[aerni]

Similar if not the same idea: #210

[jasonvarga]

The top level fields issue is a complicated one.

We don't have a good way to know if you want to override just a nested key(s) or the whole thing.

[aerni]

Yeah, I figured. Another beefy idea on your table. Fun.

[duncanmcclean]

Just came across this issue... it's now possible using the Group fieldtype.