Issue Feature Rejected

#82019Accept array instead of CSV in TCA

Mathias Brodala 08/01/17, 14:14 updated 01/10/25, 11:01

Description

There are various locations in TCA which require a CSV string of values, e.g. ctrl/searchFields or types/N/showitem.

To make it easer to handle this e.g. in Git one can use a multi-line string or the implode() function to convert an array of strings back to an CSV string.

Arrays of strings should be supported natively here to streamline TCA config.

Reviews 0

No change resolves or names this issue in its commit message, and no comment links one.

History 3

  1. Susanne Moog changed category 03/25/20, 13:58

  2. Georg Ringer commented and changed status New Rejected 01/10/25, 09:47

    Hey Mathias,

    to cleanup forge a bit I am closing this issue! You can – as explained – already use implode in your custom TCA to simplify it for you.

    adding on some places array options would mean to bloat the code just because we can. this feels wrong.

    as nothing happened in the last 7 years, I think nothing will happen in the next time

  3. Mathias Brodala commented 01/10/25, 11:01

    I don’t really understand that reasoning. Newly introduced code avoids CSV strings for the well-known reasons. So it makes sense to migrate old code from CSV to more structured formats. This could be defined as a long-term goal and would surely touch many locations.