I was having an issue where the import would fail and checking the item object on an afterParse event the headers of the csv were not being mapped accordingly.
It was a silly mistake on the csv or on the csv export that there was an extra space added by the end of some of the headers.
Adding a simple trim to the CsvParser solved the issue. I know it's very minor and stupid mistake, but this are hand made csvs and prone to mistakes so I want to make sure that my import won't run because of that. Couldn't find any other way of trimming/altering the headers before the import and it was so minor that wouldn't justify a custom Parser.
Needs work
Code
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
The commit I added was just to pull in the latest dev branch changes and fix the associated merge conflict.
The new tests seem to still be failing, though I didn't piece together what may need to be changed in the CSV Parser to resolve this.