Allow users to enter custom list of items for each content item

[mdameer]

Is your feature request related to a problem? Please describe.

Currently, no field allows users to enter a custom list of items for each content item.

Describe the solution you'd like

Enhance the MultiTextField with a new editor called EditableList, which will let users define default items (Array of strings not options like current editors) for new content items, then can be managed from the content item edit screen, allowing users to add, remove, or edit items as needed.

Describe alternatives you've considered

Adding a new field to handle this feature, but extending MultiTextField seems feasible and efficient.

[Piedone]

What's your use case, exactly? Also, wouldn't Taxonomies cover this?

[mdameer]

@Piedone I have a case where I want to add a list of items to describe the content item but without restricting the user to have all those items predefined in the field settings, so he can add different list per content item, like this image:

[Piedone]

I understand what you'd like to do, but I don't understand why you'd like to do it. If you can explain it, it would help all of us assess better how to address your needs, what might not be doing exactly what you envision right now.

[hishamco]

Currently, no field allows users to enter a custom list of items for each content item.

Why you didn't use ContentItemList?

[sebastienros]

We said we would never do this because it would mean we'd need to do it for any field type. You can use a bagpart for that. Or you can come with a better solution that would allow any field to be wrapped in a custom multi-everything editor. But it's a bag part ...

[github-actions]

We triaged this issue and set the milestone according to the priority we think is appropriate (see the docs on how we triage and prioritize issues).

This indicates when the core team may start working on it. However, if you'd like to contribute, we'd warmly welcome you to do that anytime. See our guide on contributions here.

[github-actions]

It seems that this issue didn't really move for quite a while despite us asking the author for further feedback. Is this something you'd like to revisit any time soon or should we close? Please reply.

[github-actions]

Closing this issue because it didn't receive further feedback from the author for very long. If you think this is still relevant, feel free to reopen it with the requested details.