# List type feedback

## To Consider

### Single vs List Selection

Consider introducing a selection between single items and list items before determining the item type. This would simplify user interactions. I worry that the sub-list might create confusion due to the same data types existing outside of list type (For example, text and list of text)


Unlike platforms like Airtable, where the list type is essentially text, our approach would involve actual data type validation and specialized inputs. With this in mind, I propose that being specific about the type of list would be more advantageous. It avoids implying that switching between different list types is a seamless or casual operation.

One idea would be to not have a specific 'list' type. Instead, label the types as 'list of emails', 'list of money', 'list of numbers', etc., to provide more explicit context for the user.

### Visualizing multidimensional arrays

For displaying multidimensional arrays, what you are proposing may be confusing for users.

If we're treating multidimensional arrays as strings, ensure they are purely represented as strings.

The interactive 'pill' representation for strings should be removed. This creates a false affordance that could potentially mislead users.

## Questions

- Can we detect when the array is multidimensional vs. one-dimensional?