Description
Lists created or imported through the API can store standard list types using non-canonical casing, such as individual or segment.
The participant list tables display these values correctly because their formatting is case-insensitive. However, the Edit List modal expects the exact values Individual and Segment. As a result, the Type field is not selected and the Values field may appear empty.
Experiment legacy list-type inference can also return these lowercase values.
Example experiment: https://apps.qa-cli.net/upgrade/#/home/detail/9a165e08-a140-45f1-8b03-a1aef241a447
Expected behavior
The Edit List modal should correctly populate the Type and Values fields for supported list types regardless of casing.
API write paths should validate or normalize standard list types to a consistent canonical value.
Actual behavior
Opening an existing list with a lowercase or otherwise non-canonical listType can show empty Type and Values fields and disable saving.
Description
Lists created or imported through the API can store standard list types using non-canonical casing, such as
individualorsegment.The participant list tables display these values correctly because their formatting is case-insensitive. However, the Edit List modal expects the exact values
IndividualandSegment. As a result, the Type field is not selected and the Values field may appear empty.Experiment legacy list-type inference can also return these lowercase values.
Example experiment: https://apps.qa-cli.net/upgrade/#/home/detail/9a165e08-a140-45f1-8b03-a1aef241a447
Expected behavior
The Edit List modal should correctly populate the Type and Values fields for supported list types regardless of casing.
API write paths should validate or normalize standard list types to a consistent canonical value.
Actual behavior
Opening an existing list with a lowercase or otherwise non-canonical
listTypecan show empty Type and Values fields and disable saving.