- Issue created by @joelpittet
- Merge request !9🐛 Fix: Use row style option to trigger description_field fallback → (Merged) created by joelpittet
- 🇨🇦Canada joelpittet Vancouver
The duplicate set description is already solved on dev
When building events, description_field can be empty. In this case, date_ical interprets the empty value as if the field setting itself were empty and falls back to rendering the description using the row's available fields. If one of those fields is an array, it gets string-cast when being joined with "\n", resulting in the literal text Array appearing in the exported .ics.
In the reported case, the body field was chosen for description_field but contained no content. This triggered the fallback logic, and one of the other displayed fields in the row caused the unwanted Array output. The issue was worked around by excluding non-body fields from output so that the row no longer contained the problematic field.
This appears distinct from #3477349 🐛 Descriptions with newline characters cause invalid ics files to be generated Active (newline/folding compliance). That issue is about RFC 5545 line folding/escaping of plain text, whereas this is about empty-field fallback and array casting.
description_field to point to a field (e.g., body) that is empty on a given row.description_field unless explicitly desired.Array when an array field is included in fallback rendering.description_field is set but empty, treat it as an intentional empty description rather than falling back to other fields.description_field.Active
4.0
iCal Export
The duplicate set description is already solved on dev