My new format credit card statement causes further problems. It produces a date with no year, like "15 Aug". To avoid an on-going need to edit every entry, it would be good if the CSV importer could cope with this format, please. Thanks Allan Reproducible: Always
Is this really something we want KMM to handle, or should this be handled by one of the KDE Frameworks we rely on, in which case this bug could be UPSTREAM?
AFAICT there is no KDE framework involved here. It is the CSV importer which provides a QDate object in the end and that *must* contain a year. So it is the task of the CSV importer to provide it. In a similar scenario I used the following logic in case the year information was missing: - Use currentYear as the value for statementDate - If currentMonth < statementMonth decrement year Anything else must be handled externally before the import.