When kfilemetadata starts to deliver some properties as string lists clients will need to adapt.
A list of components affected, please complete
| component | string list handling | state | responsible | future plans |
| kfilemetadata | all unit tests are against plain strings | | | |
| kfilemetadata/taglib | broken, puts out strings when there should be stringlists| wip | @astippich | | | better tests, adapt properties to their correct value types |
| baloo | ignores stringlists with more than one entry | searching breaks, fixed in D12932 | @astippich | |
| baloo | ignores stringstringlists are retrieved as qvariantlists with more than one entry | searching breaks | @michaelh | adapt | when loaded from database | toStringList() works on both, so no harm | | |
| baloo widgets | join `', '` | not yet submitted | @michaelh | use tagswidget for `subject` and `keywords`, join persons with ` & ` otherwise `, ` |@astippich | use a generic implementation in KFileMetaData |
| elisa | join `', '` | submitted | | |
| dolphin | join `', '` | already checks for properties being stringlists | | use a generic implementation in KFileMetaData |
Order of steps to be taken.
# Adapt `Baloo`
# Add generic implementation to display strings to `KFileMetaData`
# Adapt `Baloo-Widgets` & `Dolphin`
# Adapt `baloo`# Finally output QStringLists in KFileMetaData