List - collection of fields

[RWDevelopment]

It is not an original idea. This field is used to create collections of fields. It is like Grav CMS list
This kind of field allows to add any Formwork CMS fields to make complex collection of fileds.

eg.

imageGallery:
  type: list
  label: 'Gallery'
  fields:
    .text:
      type: text
      label: `Text`
    .image:
      type: image
      label: 'Image item'
    .description:
      type: textarea
      label: 'Image description'

This field can exchange array field or exist simultaneously with it.

[sgirard84]

This would be great. I had use cases for this.

[giuscris]

Definitely a nice to have.

I'm just curious about the use cases, what would you use this field for?
I'd use it for the homepage sections in getformwork.org. By now they're not editable from the panel.

Some time ago I tried to implement this, the only problem is it takes time since we need to decouple the field initialization logic from form.ts to create new field instances and correctly initialize events, independently from forms.

@RWDevelopment I'm not sure why you added dot prefixes to the field names.

I think it can be integrated as an enhanced array field. We already can enable or disable the key field, this enhancement will only change the value part.

[sgirard84]

For me, I was thinking about such field (an advanced array field) in a photography website.

Photo image scheme:

• image
• title
• description
• tags
• purchase options (array field)
  • name
  • product type
  • [etc]

Obviously this scenario would work better with another form of storage like a DB with proper normalised structure with each entity in separate tables, with reference keys.

But for for micro website, this would work while maintaining the system easy manage.

[RWDevelopment]

Definitely a nice to have.

I'm just curious about the use cases, what would you use this field for? I'd use it for the homepage sections in getformwork.org. By now they're not editable from the panel.

Some time ago I tried to implement this, the only problem is it takes time since we need to decouple the field initialization logic from form.ts to create new field instances and correctly initialize events, independently from forms.

@RWDevelopment I'm not sure why you added dot prefixes to the field names.

I think it can be integrated as an enhanced array field. We already can enable or disable the key field, this enhancement will only change the value part.

This field can be used for any repeatable content with complex data structure e.g. like sections, galleries, timelines ... of course it can be done with page children for example or as you said 'an enhanced array field', but i think it is the same - this field is an enhanced array field.

Dot prefixes to the field names mean nothing, it's just copied from Grav's example.

Maybe instead of list field it can be a JSON / YAML field with editor, where you can prepare complex data structure you need, and i think it will be easier to implement.